investigate_issue · Sentry Investigator MCP: Risk & Policy

WHAT IT DOES

What investigate_issue does on Sentry Investigator

AI agents use investigate_issue to create or update resources in Sentry Investigator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sentry Investigator environment.

WHY IT NEEDS A POLICY

Why investigate_issue needs a policy

An AI agent can call investigate_issue faster than any human can review — one bad instruction and it creates or modifies resources in Sentry Investigator by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

investigate_issue Rate-limited

investigate_issue stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "investigate_issue": {
      "limits": [
        {
          "counter": "investigate_issue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sentry Investigator, so you can run agents against it safely.

FAQ

Questions about investigate_issue

What does the investigate_issue tool do? +

Investigate a specific Sentry issue by analyzing the codebase and providing explanations and fixes. It is categorised as a Write tool in the Sentry Investigator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on investigate_issue? +

Register the Sentry Investigator MCP server in PolicyLayer and add a rule for investigate_issue: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Sentry Investigator. Nothing to install.

What risk level is investigate_issue? +

investigate_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit investigate_issue? +

Yes. Add a rate_limit block to the investigate_issue rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block investigate_issue completely? +

Set action: deny in the PolicyLayer policy for investigate_issue. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides investigate_issue? +

investigate_issue is provided by the Sentry Investigator MCP server (vibe-code-agent/sentry-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.