Rename a running VM by changing its label. The label is used for snapshot naming — renaming does NOT migrate existing snapshots (they stay under the old label).
AI agents use vm_rename to create or update resources in Taw Computer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Taw Computer environment.
The tool modifies VM labels/names, which is a reversible write operation. It does not delete data, execute arbitrary commands, or cause financial impact. The clarification that snapshots are not migrated indicates this is a safe, non-destructive rename operation. Severity is low because renaming a VM label has minimal blast radius—it affects only labeling conventions, not data integrity or system functionality.
From the tool's definition Tool description states it 'Rename a running VM by changing its label' and 'renaming does NOT migrate existing snapshots (they stay under the old label)'. This is a metadata modification operation.
Documented attack patterns abuse exactly the kind of access vm_rename 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_rename:
{
"version": "1",
"default": "deny",
"tools": {
"vm_rename": {
"limits": [
{
"counter": "vm_rename_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}vm_rename stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Rename a running VM by changing its label. The label is used for snapshot naming — renaming does NOT migrate existing snapshots (they stay under the old label). It is categorised as a Write tool in the Taw Computer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Taw Computer MCP server in PolicyLayer and add a rule for vm_rename: 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_rename is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vm_rename 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_rename. 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_rename 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.