vm_list
List all virtual machines on the TrueNAS system, including their configuration and status.
This record as markdown: /tools/nasbridge/vm-list.md
What vm_list does on Nasbridge
AI agents call vm_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.
Why vm_list is rated Low
This tool performs a read-only query to enumerate virtual machines and their properties. It retrieves information without creating, modifying, deleting, or executing anything. The blast radius is minimal as it only exposes system inventory data.
From the tool's definition Tool name 'vm_list' and description 'List all virtual machines on the TrueNAS system, including their configuration and status' indicate a data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs vm_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_list, this is the rule to start with:
vm_list is read-only, so it stays allowed. 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_list call is checked against it from then on.
Questions about vm_list
List all virtual machines on the TrueNAS system, including their configuration and status. It is categorised as a Read tool in the Nasbridge MCP Server, which means it retrieves data without modifying state.
Register the Nasbridge MCP server in PolicyLayer and add a rule for vm_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.
vm_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vm_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.
Set action: deny in the PolicyLayer policy for vm_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.
vm_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.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue