New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

vm_device_update

Update an existing VM device by its ID. Provide any fields to change (dtype, attributes, order, vm).

SERVERNasbridge SOURCEmaverick0628/nasbridge
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nasbridge/vm-device-update.md

What vm_device_update does on Nasbridge

AI agents use vm_device_update to create or update resources in Nasbridge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nasbridge 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).

Questions about vm_device_update

What does the vm_device_update tool do? +

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 Nasbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on vm_device_update? +

Register the Nasbridge 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 Nasbridge. Nothing to install.

What risk level is vm_device_update? +

vm_device_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit vm_device_update? +

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.

How do I block vm_device_update completely? +

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.

What MCP server provides vm_device_update? +

vm_device_update is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Nasbridge, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nasbridge's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.