vm_update

Update an existing 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-update.md

WHAT IT DOES

What vm_update does on Nasbridge

AI agents use vm_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.

RISK

Why vm_update is rated Medium

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vm_update safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vm_update, this is the rule to start with:

vm_update Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vm_update": {
      "limits": [
        {
          "counter": "vm_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every vm_update call is checked against it from then on.

FAQ

Questions about vm_update

What does the vm_update tool do? +

Update an existing 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_update? +

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

What risk level is vm_update? +

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

Can I rate-limit vm_update? +

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.

How do I block vm_update completely? +

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.

What MCP server provides vm_update? +

vm_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.

KEEP EXPLORING

More on Nasbridge, and thousands of servers like it.

This server

All 279 Nasbridge tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →