Low Risk

enhancement_telemetry

Get telemetry data for prompt enhancement (success rate, cache hits, latency)

How to control enhancement_telemetry ↓

What enhancement_telemetry does on MCP Codebase Index

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

Low Risk

Why enhancement_telemetry needs a policy

This tool gathers metrics and monitoring data without side effects. No data is created, modified, deleted, or executed. It falls squarely into the Read category as a diagnostic/observability function. Severity is low because telemetry data is non-critical operational metadata with no impact on core systems or user data if misused.

From the tool's definition Tool retrieves telemetry data for monitoring purposes (success rate, cache hits, latency). The description indicates querying/inspection only with no modification, deletion, or execution capability.

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

How to control enhancement_telemetry

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

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

enhancement_telemetry 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 Codebase Index — 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.

Related tools and policies

Go deeper

Questions about enhancement_telemetry

What does the enhancement_telemetry tool do? +

Get telemetry data for prompt enhancement (success rate, cache hits, latency). It is categorised as a Read tool in the MCP Codebase Index MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on enhancement_telemetry? +

Register the MCP Codebase Index MCP server in PolicyLayer and add a rule for enhancement_telemetry: 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 Codebase Index. Nothing to install.

What risk level is enhancement_telemetry? +

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

Can I rate-limit enhancement_telemetry? +

Yes. Add a rate_limit block to the enhancement_telemetry 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 enhancement_telemetry completely? +

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

enhancement_telemetry is provided by the MCP Codebase Index MCP server (ngotaico/mcp-codebase-index). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Codebase Index tool call.

Start from MCP Codebase Index, 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.

9 MCP Codebase Index tools catalogued and risk-classified — across an index of 43,000+ 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.