Compare two analyses to see score changes and new/fixed issues
AI agents call compare_analyses 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.
The tool retrieves and displays differences between two pre-existing analyses. It has no side effects, does not execute code, does not modify data, and does not delete anything. It is a read-only operation that queries and presents comparative information about analysis results. This falls squarely into the 'Read' category as a data retrieval operation.
From the tool's definition The tool 'compare_analyses' performs a comparison operation that 'see[s] score changes and new/fixed issues' between two existing analyses. This is purely a retrieval and comparison of data with no modification, creation, or deletion of any resources.
Attacks that exploit this kind of access
Compare two analyses to see score changes and new/fixed issues. 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 compare_analyses: 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.
compare_analyses 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 compare_analyses 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 compare_analyses. 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.
compare_analyses 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 →