Low Risk

vm_clone

Clone a KubeVirt VirtualMachine by creating a VirtualMachineClone resource. This creates a copy of the source VM with a new name using the KubeVirt Clone API

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

AI agents call vm_clone to retrieve information from Kubernetes without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though vm_clone only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-containers-kubernetes-mcp-server.yaml
tools:
  vm_clone:
    rules:
      - action: allow

See the full Kubernetes policy for all 37 tools.

Tool Name vm_clone
Category Read
Risk Level Low

View all 37 tools →

Agents calling read-class tools like vm_clone 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 Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the vm_clone tool do? +

Clone a KubeVirt VirtualMachine by creating a VirtualMachineClone resource. This creates a copy of the source VM with a new name using the KubeVirt Clone API. It is categorised as a Read tool in the Kubernetes MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vm_clone? +

Add a rule in your Intercept YAML policy under the tools section for vm_clone. 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_clone? +

vm_clone is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vm_clone? +

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

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

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