High Risk →

vm_lifecycle

Manage VirtualMachine lifecycle: start, stop, or restart a VM

Part of the Kubernetes MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

kubernetes-mcp-server Execute Risk 3/5

AI agents invoke vm_lifecycle to trigger processes or run actions in Kubernetes. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

vm_lifecycle can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-containers-kubernetes-mcp-server.yaml
tools:
  vm_lifecycle:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Kubernetes policy for all 37 tools.

Tool Name vm_lifecycle
Category Execute
Risk Level High

View all 37 tools →

Agents calling execute-class tools like vm_lifecycle have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

vm_lifecycle is one of the high-risk operations in Kubernetes. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the vm_lifecycle tool do? +

Manage VirtualMachine lifecycle: start, stop, or restart a VM. It is categorised as a Execute tool in the Kubernetes MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vm_lifecycle? +

Add a rule in your Intercept YAML policy under the tools section for vm_lifecycle. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kubernetes MCP server.

What risk level is vm_lifecycle? +

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

Can I rate-limit vm_lifecycle? +

Yes. Add a rate_limit block to the vm_lifecycle rule in your Intercept 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 vm_lifecycle completely? +

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

vm_lifecycle is provided by the Kubernetes MCP server (kubernetes-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Kubernetes

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.