k8s_exec · Yaver MCP: Risk & Policy

WHAT IT DOES

What k8s_exec does on Yaver

AI agents invoke k8s_exec to trigger actions in Yaver. 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.

PARAMETERS

Parameter	Type	Required
`pod`	string	Yes
`command`	string	Yes
`context`	string	—
`container`	string	—
`namespace`	string	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why k8s_exec needs a policy

k8s_exec triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAccepts freeform code/query input (command)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

k8s_exec Rate-limited

k8s_exec 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": {
    "k8s_exec": {
      "limits": [
        {
          "counter": "k8s_exec_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 Yaver, so you can run agents against it safely.

FAQ

Questions about k8s_exec

What does the k8s_exec tool do? +

Execute a command in a Kubernetes pod. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does k8s_exec accept? +

k8s_exec accepts 5 parameters: pod, command, context, container, namespace. Required: pod, command. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on k8s_exec? +

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

What risk level is k8s_exec? +

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

Can I rate-limit k8s_exec? +

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

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

k8s_exec is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.