Investigate an error by finding the code owner and related pull requests.
AI agents call investigate_error to retrieve information from Error Tracker MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The investigate_error tool performs lookups and queries (finding code owners, retrieving pull request information) with no capability to modify, delete, or execute operations. It is purely informational/analytical in nature, making it a Read category tool with low severity since data retrieval poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states it 'finding the code owner and related pull requests' - both read-only operations that retrieve data without modification or side effects.
Attacks that exploit this kind of access
Investigate an error by finding the code owner and related pull requests. It is categorised as a Read tool in the Error Tracker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Error Tracker MCP Server MCP server in PolicyLayer and add a rule for investigate_error: 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 Error Tracker MCP Server. Nothing to install.
investigate_error 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 investigate_error 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 investigate_error. 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.
investigate_error is provided by the Error Tracker MCP Server MCP server (wyccome/mcp-error-tracing). 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 →