Fetch a specific Kubernetes runbook by topic
AI agents call fetch-runbook to retrieve information from Kubernetes Runbooks without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing Kubernetes troubleshooting documentation. Fetching a runbook is a read-only operation that queries and returns information without modifying, deleting, or executing anything. There is no capability to alter system state or trigger external operations. The low severity reflects minimal risk—misuse would only expose documentation that is typically intended to be shared.
From the tool's definition The tool 'fetch-runbook' is described as 'Fetch a specific Kubernetes runbook by topic' and operates within a server that provides 'search, discovery, and retrieval of guides'.
Attacks that exploit this kind of access
Fetch a specific Kubernetes runbook by topic. It is categorised as a Read tool in the Kubernetes Runbooks MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes Runbooks MCP server in PolicyLayer and add a rule for fetch-runbook: 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 Kubernetes Runbooks. Nothing to install.
fetch-runbook 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 fetch-runbook 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 fetch-runbook. 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.
fetch-runbook is provided by the Kubernetes Runbooks MCP server (raihan0824/kubernetes-runbooks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →