AI agents call vm_list to retrieve information from Taw Computer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple enumeration of existing sandbox instances. It has no side effects, does not execute code or commands, and does not modify state. The blast radius of misuse is minimal—an agent listing sandboxes cannot cause harm beyond information disclosure of what sandboxes exist in the current session.
From the tool's definition Tool name 'vm_list' and description 'List active sandboxes created in this MCP session' indicate a read-only query operation that retrieves information about existing sandboxes without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access vm_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Taw Computer, and nothing reaches the server without passing your rules. This is the rule we recommend for vm_list:
{
"version": "1",
"default": "deny",
"tools": {
"vm_list": {}
}
}vm_list 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.
List active sandboxes created in this MCP session. It is categorised as a Read tool in the Taw Computer MCP Server, which means it retrieves data without modifying state.
Register the Taw Computer MCP server in PolicyLayer and add a rule for vm_list: 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 Taw Computer. Nothing to install.
vm_list 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_list 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_list. 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_list is provided by the Taw Computer MCP server (tawgroup/taw-computer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Taw Computer, 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.
36 Taw Computer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.