AI agents call calculate-metrics to retrieve information from CodeAnalysis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Metrics calculation is a read-only analytical operation that queries or processes code without modifying data or executing external operations. The tool retrieves measurements and produces analysis artifacts. Given the empty description and reliance on the tool name and server context, confidence is slightly reduced from 0.9 to 0.85, but the pattern is clear from sibling tools and the 'analysis' focus of the server.
From the tool's definition Tool name 'calculate-metrics' and server context indicates analysis/measurement operations. Server description emphasizes 'code analysis' and 'metrics' is explicitly listed as a sibling tool (analyze-metrics).
Documented attack patterns abuse exactly the kind of access calculate-metrics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeAnalysis MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for calculate-metrics:
{
"version": "1",
"default": "deny",
"tools": {
"calculate-metrics": {}
}
}calculate-metrics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
calculate-metrics. It is categorised as a Read tool in the CodeAnalysis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CodeAnalysis MCP Server MCP server in PolicyLayer and add a rule for calculate-metrics: 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 CodeAnalysis MCP Server. Nothing to install.
calculate-metrics 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 calculate-metrics 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 calculate-metrics. 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.
calculate-metrics is provided by the CodeAnalysis MCP Server MCP server (0xjcf/mcp_codeanalysis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeAnalysis MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
31 CodeAnalysis MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.