Low Risk

analyze_code_quality

分析代码质量指标

How to control analyze_code_quality ↓

AI agents call analyze_code_quality to retrieve information from MCP Code Indexer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool performs static analysis to retrieve and compute quality metrics about code. It retrieves information and produces reports but has no side effects—no code is executed, modified, or deleted. This is a read operation in the context of a code indexing/analysis server.

From the tool's definition The tool name is "analyze_code_quality" and the description translates to "analyze code quality metrics." The sibling tools on this server are all read-only operations: search_code, find_similar_code, get_code_structure, get_code_metrics, identify_project,…

Documented attack patterns abuse exactly the kind of access analyze_code_quality gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Code Indexer, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_code_quality:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_code_quality": {}
  }
}

analyze_code_quality is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Code Indexer — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the analyze_code_quality tool do? +

分析代码质量指标. It is categorised as a Read tool in the MCP Code Indexer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analyze_code_quality? +

Register the MCP Code Indexer MCP server in PolicyLayer and add a rule for analyze_code_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 MCP Code Indexer. Nothing to install.

What risk level is analyze_code_quality? +

analyze_code_quality is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit analyze_code_quality? +

Yes. Add a rate_limit block to the analyze_code_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.

How do I block analyze_code_quality completely? +

Set action: deny in the PolicyLayer policy for analyze_code_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.

What MCP server provides analyze_code_quality? +

analyze_code_quality is provided by the MCP Code Indexer MCP server (zxfgds/mcp-code-indexer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Code Indexer tool call.

Deterministic rules across all 8 MCP Code Indexer tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

8 MCP Code Indexer tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.