Get a detailed report for a completed analysis
AI agents call get_analysis_report to retrieve information from MCP Code Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing analysis data without creating, modifying, executing, deleting, or moving money. It has no side effects beyond providing information. The blast radius of misuse is minimal—an agent could over-query or access reports it shouldn't, but cannot alter the system, execute code, or cause irreversible damage through this tool alone.
From the tool's definition The tool 'gets' a detailed report for a completed analysis, which is a retrieval operation with no modification or execution capability. The verb 'get' and the context of retrieving a report clearly indicate a read-only action.
Attacks that exploit this kind of access
Get a detailed report for a completed analysis. It is categorised as a Read tool in the MCP Code Analyzer MCP Server, which means it retrieves data without modifying state.
Register the MCP Code Analyzer MCP server in PolicyLayer and add a rule for get_analysis_report: 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 Code Analyzer. Nothing to install.
get_analysis_report 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 get_analysis_report 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 get_analysis_report. 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.
get_analysis_report is provided by the MCP Code Analyzer MCP server (polocap/mcp_security). 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 →