Analyze a stack trace and find related code in the codebase
AI agents call analyze_stack_trace to retrieve information from Sentry Investigator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and analyzes existing stack trace data and searches the codebase for relevant code sections. It has no side effects—it does not modify data, execute code, delete anything, or trigger financial operations. The action is purely informational and investigative in nature, making it a Read category tool with low severity.
From the tool's definition Tool performs analysis and finding of related code in the codebase. The verb 'analyze' combined with 'find related code' indicates data retrieval and examination without modification or execution of code.
Attacks that exploit this kind of access
Analyze a stack trace and find related code in the codebase. It is categorised as a Read tool in the Sentry Investigator MCP Server, which means it retrieves data without modifying state.
Register the Sentry Investigator MCP server in PolicyLayer and add a rule for analyze_stack_trace: 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.
analyze_stack_trace is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the analyze_stack_trace 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.
Set action: deny in the PolicyLayer policy for analyze_stack_trace. 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.
analyze_stack_trace 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →