AI agents call vm_status to retrieve information from tmux-claude MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves VM status information without altering system state, executing commands, or triggering external operations. It is a straightforward information lookup, consistent with the Read category pattern of non-destructive data retrieval.
From the tool's definition Tool name 'vm_status' and description 'Get detailed status of a VM instance' indicate a read-only query operation that retrieves information without modification or side effects.
Documented attack patterns abuse exactly the kind of access vm_status 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_status:
{
"version": "1",
"default": "deny",
"tools": {
"vm_status": {}
}
}vm_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed status of a VM instance. It is categorised as a Read tool in the tmux-claude MCP Server MCP Server, which means it retrieves data without modifying state.
Register the tmux-claude MCP Server MCP server in PolicyLayer and add a rule for vm_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vm_status 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_status. 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_status 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.