vm_restart
Restart a running virtual machine by its ID.
This record as markdown: /tools/nasbridge/vm-restart.md
What vm_restart does on Nasbridge
AI agents invoke vm_restart to trigger actions in Nasbridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why vm_restart is rated High
Restarting a VM is an executable action that affects running infrastructure and services, potentially causing downtime and service disruption. While not destructive or financial, it modifies system state and has external operational consequences.
From the tool's definition Tool name 'vm_restart' and description 'Restart a running virtual machine by its ID' indicate this triggers an external operation (VM restart) whose effects depend on the provided VM ID argument.
Attacks that exploit this kind of access
The rule that runs vm_restart 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_restart, this is the rule to start with:
vm_restart stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every vm_restart call is checked against it from then on.
Questions about vm_restart
Restart a running virtual machine by its ID. It is categorised as a Execute tool in the Nasbridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nasbridge MCP server in PolicyLayer and add a rule for vm_restart: 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.
vm_restart is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vm_restart 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_restart. 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_restart 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.
Across the catalogue