AI agents call wait_for_vm to retrieve information from Mcp Utm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool waits and observes the VM status, which is a read/polling operation with no side effects. It does not modify, create, delete, or execute anything. Low severity as misuse would at most cause a blocking wait.
From the tool's definition 'Wait until a VM reaches a target status' — the tool monitors/polls VM state without modifying anything
Attacks that exploit this kind of access
Wait until a VM reaches a target status. It is categorised as a Read tool in the Mcp Utm MCP Server, which means it retrieves data without modifying state.
Register the Mcp Utm MCP server in PolicyLayer and add a rule for wait_for_vm: 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 Mcp Utm. Nothing to install.
wait_for_vm 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 wait_for_vm 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 wait_for_vm. 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.
wait_for_vm is provided by the Mcp Utm MCP server (neverprepared/mcp-utm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →