Create a new VM instance for Claude development
AI agents invoke vm_create to trigger actions in tmux-claude 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.
Creating a VM instance triggers external infrastructure provisioning. While not directly financial, it allocates compute resources that may incur costs and has significant blast radius if misused (e.g., spinning up many VMs). It goes beyond a simple Write as it executes an external operation with real system-level effects.
From the tool's definition 'Create a new VM instance' — spawns a virtual machine, which is an external infrastructure operation with resource and cost implications
Documented attack patterns abuse exactly the kind of access vm_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and tmux-claude MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for vm_create:
{
"version": "1",
"default": "deny",
"tools": {
"vm_create": {
"limits": [
{
"counter": "vm_create_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}vm_create 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.
Free to start. No card required.
Create a new VM instance for Claude development. It is categorised as a Execute tool in the tmux-claude MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the tmux-claude MCP Server MCP server in PolicyLayer and add a rule for vm_create: 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 tmux-claude MCP Server. Nothing to install.
vm_create is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vm_create 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 vm_create. 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.
vm_create is provided by the tmux-claude MCP Server MCP server (michael-abdo/tmux-claude-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from tmux-claude MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 tmux-claude MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.