Low Risk

get_code_metrics

获取代码度量数据

How to control get_code_metrics ↓

AI agents call get_code_metrics 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 retrieves code quality metrics or statistics from an indexed codebase. It performs no modifications, deletions, or external operations. The action is purely informational—querying existing metrics data. This aligns with the 'Read' category (retrieves or queries data; no side effects).

From the tool's definition The tool name 'get_code_metrics' and description '获取代码度量数据' (retrieves code metrics data) indicate a data retrieval operation. The context as part of a code indexing/retrieval server confirms this is a read-only query function.

Documented attack patterns abuse exactly the kind of access get_code_metrics 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 get_code_metrics:

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

get_code_metrics 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 get_code_metrics 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 get_code_metrics? +

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

What risk level is get_code_metrics? +

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

Can I rate-limit get_code_metrics? +

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

How do I block get_code_metrics completely? +

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

What MCP server provides get_code_metrics? +

get_code_metrics 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.