Fetches incident telemetry from a mock external API, including realistic stack traces and failure simulation controls.
AI agents call fetch_system_incidents to retrieve information from MCP Server Codebase Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves incident telemetry and diagnostic information. There is no indication it modifies, deletes, or executes code. The mention of 'failure simulation controls' refers to parameters that control what incident data is fetched, not operations that cause real system changes.
From the tool's definition Tool description states it 'Fetches incident telemetry from a mock external API' — the verb 'fetches' indicates data retrieval. The scope is limited to reading existing incident data and stack traces from an external API without modification.
Attacks that exploit this kind of access
Fetches incident telemetry from a mock external API, including realistic stack traces and failure simulation controls. It is categorised as a Read tool in the MCP Server Codebase Analyzer MCP Server, which means it retrieves data without modifying state.
Register the MCP Server Codebase Analyzer MCP server in PolicyLayer and add a rule for fetch_system_incidents: 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 MCP Server Codebase Analyzer. Nothing to install.
fetch_system_incidents 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 fetch_system_incidents 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 fetch_system_incidents. 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.
fetch_system_incidents is provided by the MCP Server Codebase Analyzer MCP server (kushalsai-01/mcp-server-codebase-analyser). 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 →