Low Risk

search_cdk_documentation

search_cdk_documentation

How to control search_cdk_documentation ↓

What search_cdk_documentation does on Prometheus MCP Server

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

Low Risk

Why search_cdk_documentation needs a policy

The tool name strongly suggests searching/querying documentation, which is a read-only operation with no side effects. Without a description, confidence is slightly reduced, but the naming pattern and context among sibling tools (which include search and analyze operations) support a Read classification. Low severity reflects minimal blast radius—retrieving documentation cannot modify systems or cause harm.

From the tool's definition Tool name 'search_cdk_documentation' indicates a read operation that queries or retrieves documentation. Description is empty, limiting specificity.

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

How to control search_cdk_documentation

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

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

search_cdk_documentation 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 Prometheus MCP Server — 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 search_cdk_documentation

What does the search_cdk_documentation tool do? +

search_cdk_documentation. It is categorised as a Read tool in the Prometheus MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_cdk_documentation? +

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

What risk level is search_cdk_documentation? +

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

Can I rate-limit search_cdk_documentation? +

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

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

search_cdk_documentation is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Prometheus MCP Server tool call.

Start from Prometheus 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.

805 Prometheus MCP Server 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.