A Copilot cloud agent is assigned to a GitHub issue that was created from a production exception. The repository has an MCP configuration that should allow the agent to read Sentry event details, but the agent session cannot start the Sentry MCP server. Which change should you make first? Select one answer.
Copilot cloud agent session: rel-issue-1842
Repository: octo-org/payments-api
Agent: sentry-error-fixer
Start MCP Servers
Loading repository MCP configuration
Server: sentry
Command: npx @sentry/mcp-server@latest
Env:
SENTRY_ACCESS_TOKEN=${{ secrets.COPILOT_MCP_SENTRY_ACCESS_TOKEN }}
Error: Unable to resolve secret COPILOT_MCP_SENTRY_ACCESS_TOKEN
Reason: No Agents secret or variable with this name was available
Note: GitHub Actions, Codespaces, and Dependabot secrets are not passed to Copilot cloud agent
Result: Sentry MCP tools were not startedChoose an answer
Tap an option to check your answer.
Correct answer: Add the referenced Agents secret.
Why this is the answer
The error message "Unable to resolve secret COPILOTMCPSENTRYACCESSTOKEN" and the note "No Agents secret or variable with this name was available" clearly indicate that the COPILOTMCPSENTRYACCESSTOKEN secret is missing from the Copilot Agents secrets. Copilot cloud agents do not inherit secrets from GitHub Actions, Codespaces, or Dependabot, so adding an Actions secret would not resolve this specific issue. Granting packages write to GITHUBTOKEN or removing readonly from the GitHub MCP URL are unrelated to the secret resolution problem. Therefore, the first step is to add the required secret to the Copilot Agents configuration.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed