run_runbook · Kubernetes + Prometheus SRE MCP Server MCP

WHAT IT DOES

What run_runbook does on Kubernetes + Prometheus SRE MCP Server

AI agents invoke run_runbook to trigger actions in Kubernetes + Prometheus SRE MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_runbook needs a policy

This tool runs executable procedures in a Kubernetes/SRE context. While labeled 'standardized,' runbooks often perform kubectl apply, service restarts, pod terminations, or traffic redirects whose outcomes depend on arguments and configuration. These are reversible but high-impact operations (not Destructive per se, but consequential). Misuse could disrupt production services, cause downtime, or drain resources.

From the tool's definition Tool description states 'Execute a standardized SRE runbook' — the word 'Execute' directly indicates code or operational execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_runbook Rate-limited

run_runbook stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_runbook": {
      "limits": [
        {
          "counter": "run_runbook_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kubernetes + Prometheus SRE MCP Server, so you can run agents against it safely.

FAQ

Questions about run_runbook

What does the run_runbook tool do? +

Execute a standardized SRE runbook. It is categorised as a Execute tool in the Kubernetes + Prometheus SRE MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_runbook? +

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

What risk level is run_runbook? +

run_runbook is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_runbook? +

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

How do I block run_runbook completely? +

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

What MCP server provides run_runbook? +

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