AI agents call get_vm_state to retrieve information from Virtualization without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves the state of an existing VM (e.g., running, stopped, paused). It performs no modifications, execution of code, destruction of resources, or financial operations. The blast radius of misuse is minimal—at worst, an agent gains visibility into VM status, which does not alter the system or cause harm.
From the tool's definition Tool name 'get_vm_state' and description 'Get the current state of a virtual machine' indicate a query operation that retrieves information without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_vm_state gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Virtualization, and nothing reaches the server without passing your rules. This is the rule we recommend for get_vm_state:
{
"version": "1",
"default": "deny",
"tools": {
"get_vm_state": {}
}
}get_vm_state 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 the current state of a virtual machine. It is categorised as a Read tool in the Virtualization MCP Server, which means it retrieves data without modifying state.
Register the Virtualization MCP server in PolicyLayer and add a rule for get_vm_state: 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 Virtualization. Nothing to install.
get_vm_state 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 get_vm_state 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 get_vm_state. 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.
get_vm_state is provided by the Virtualization MCP server (sandraschi/virtualization-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Virtualization, 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.
56 Virtualization tools catalogued and risk-classified — across an index of 43,000+ MCP servers.