A custom Copilot cloud agent is intended to diagnose production errors using Sentry context. The agent can read and edit repository files, but it fails when it tries to retrieve the Sentry event referenced in the issue. Evaluate the following statements. 1. The Sentry server is configured, but its tool is unavailable to the custom agent. 2. The best root cause is a reasoning error rather than a tool-permission issue. 3. The guessed fix should be treated as lower confidence because required external context was unavailable.

---
name: prod-error-fixer
description: Diagnoses production exceptions and proposes minimal fixes.
tools: ["read", "search", "edit"]
mcp-servers:
  sentry:
    type: local
    command: npx
    args: ["@sentry/mcp-server@latest"]
    env:
      SENTRY_ACCESS_TOKEN: ${{ secrets.COPILOT_MCP_SENTRY_ACCESS_TOKEN }}
---

When assigned to an issue, inspect the Sentry event ID in the issue body,
identify the failing code path, and propose the smallest safe fix.
Session result

Agent started successfully
Read issue body: SENTRY-EVENT-99482
Searched repository for matching handler names
Could not call sentry/get-event
Available tools: read, search, edit
Draft PR created with a guessed null-check fix