List all encoded SRE runbooks with their triggers
AI agents call list_runbooks to retrieve information from Kubernetes + Prometheus SRE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates SRE runbook metadata (names, triggers) from the Kubernetes cluster. It has no side effects—it does not execute runbooks, modify cluster state, or delete data. It is a simple read operation consistent with sibling tools like get_pod_logs, get_events, and get_deployments.
From the tool's definition Tool name 'list_runbooks' and description 'List all encoded SRE runbooks with their triggers' indicate a query/retrieval operation.
Attacks that exploit this kind of access
List all encoded SRE runbooks with their triggers. It is categorised as a Read tool in the Kubernetes + Prometheus SRE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes + Prometheus SRE MCP Server MCP server in PolicyLayer and add a rule for list_runbooks: 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 + Prometheus SRE MCP Server. Nothing to install.
list_runbooks 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 list_runbooks 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 list_runbooks. 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.
list_runbooks is provided by the Kubernetes + Prometheus SRE MCP Server MCP server (manishmaurya22/sre-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 →