vm_device_update
Update an existing VM device by its ID. Provide any fields to change (dtype, attributes, order, vm).
This record as markdown: /tools/spranab-truenas-mcp/vm-device-update.md
What vm_device_update does on Truenas
AI agents use vm_device_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.
Why vm_device_update is rated Medium
This tool modifies VM device configuration through an update operation. While it creates or modifies data reversibly (matching Write), the severity is elevated to 'high' because: (1) VM device modifications directly affect virtual machine functionality, networking, storage, or resource allocation; (2) incorrect updates could cause service disruption or VM downtime; (3) TrueNAS is a production-critical…
From the tool's definition Update an existing VM device by its ID. Provide any fields to change (dtype, attributes, order, vm).
Attacks that exploit this kind of access
The rule that runs vm_device_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vm_device_update, this is the rule to start with:
vm_device_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Truenas, apply this rule, and every vm_device_update call is checked against it from then on.
Questions about vm_device_update
Update an existing VM device by its ID. Provide any fields to change (dtype, attributes, order, 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_device_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_device_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_device_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_device_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_device_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.
More on Truenas, and thousands of servers like it.
This server
Across the catalogue