AI agents use vm_update to create or update resources in Truenas — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Truenas environment.
This tool modifies VM settings or configuration. While VMs are critical infrastructure, the update operation itself is reversible and does not permanently destroy data or execute arbitrary code on the host. However, severity is elevated to 'high' due to the blast radius: misconfigured VM updates could impact services, networking, or resource allocation affecting multiple workloads.
From the tool's definition Tool name 'vm_update' and description 'Update an existing VM' indicate modification of VM configuration/state. The verb 'update' is characteristic of reversible Write operations.
Documented attack patterns abuse exactly the kind of access vm_update gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Truenas, and nothing reaches the server without passing your rules. This is the rule we recommend for vm_update:
{
"version": "1",
"default": "deny",
"tools": {
"vm_update": {
"limits": [
{
"counter": "vm_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}vm_update 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.
Update an existing VM. It is categorised as a Write tool in the Truenas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Truenas MCP server in PolicyLayer and add a rule for vm_update: 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 Truenas. Nothing to install.
vm_update 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_update 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_update. 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_update is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Truenas, 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.
279 Truenas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.