vm_device_list

List VM devices. Optionally filter by VM ID to see devices attached to a specific VM.

SERVERNasbridge SOURCEmaverick0628/nasbridge

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What vm_device_list does on Nasbridge

AI agents call vm_device_list to retrieve information from Nasbridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why vm_device_list is rated Low

This is a read-only operation that retrieves information about VM devices. It performs no modifications, deletions, code execution, or financial transactions. The optional filtering by VM ID is a query parameter that does not alter system state. Blast radius is minimal as it only exposes infrastructure visibility information.

From the tool's definition Tool name 'vm_device_list' and description 'List VM devices' indicates data retrieval without side effects. The action is to query/enumerate devices attached to virtual machines.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vm_device_list 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_device_list, this is the rule to start with:

vm_device_list Allowed

vm_device_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vm_device_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about vm_device_list

What does the vm_device_list tool do? +

List VM devices. Optionally filter by VM ID to see devices attached to a specific VM. It is categorised as a Read tool in the Nasbridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vm_device_list? +

Register the Nasbridge MCP server in PolicyLayer and add a rule for vm_device_list: 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_list? +

vm_device_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vm_device_list? +

Yes. Add a rate_limit block to the vm_device_list 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_list completely? +

Set action: deny in the PolicyLayer policy for vm_device_list. 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_list? +

vm_device_list 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →