Update VM configuration (RAM, CPUs, etc.).
AI agents use update_vm to create or update resources in Truenas Ws — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Truenas Ws environment.
This tool modifies VM configuration parameters (RAM, CPUs) but does not delete VMs or irreversibly destroy data. Changes to VM resources are reversible — an admin can adjust RAM or CPU counts again. This is a Write operation rather than Destructive.
From the tool's definition Tool description states 'Update VM configuration (RAM, CPUs, etc.)' — this modifies VM settings reversibly. The sibling tools (create_dataset, create_snapshot, create_user) confirm this server performs state-changing operations.
Attacks that exploit this kind of access
Update VM configuration (RAM, CPUs, etc.). It is categorised as a Write tool in the Truenas Ws MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Truenas Ws MCP server in PolicyLayer and add a rule for update_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 Truenas Ws. Nothing to install.
update_vm 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 update_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 update_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.
update_vm is provided by the Truenas Ws MCP server (thoriphes/truenas-ws-mcp). 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 →