AI agents call analyze-quality 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.
Despite the empty description, the tool appears to perform code quality analysis without side effects. The server is explicitly described as providing 'syntax analysis, dependency visualization, and AI-assisted development workflow support'—all read operations. The tool sits among sibling analysis and metric calculation tools, and 'analyze-quality' follows the same naming convention as other read-only analysis tools.
From the tool's definition Tool name 'analyze-quality' combined with sibling tools that are all analysis/read operations (analyze-cursor, analyze-dependencies, analyze-files, analyze-metrics, analyze-repository, build-knowledge-graph, calculate-metrics).
Documented attack patterns abuse exactly the kind of access analyze-quality 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 analyze-quality:
{
"version": "1",
"default": "deny",
"tools": {
"analyze-quality": {}
}
}analyze-quality 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.
analyze-quality. 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 analyze-quality: 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.
analyze-quality 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 analyze-quality 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 analyze-quality. 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.
analyze-quality 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.