vm_get
Get detailed information about a specific VM by its numeric ID.
This record as markdown: /tools/spranab-truenas-mcp/vm-get.md
What vm_get does on Truenas
AI agents call vm_get to retrieve information from Truenas without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why vm_get is rated Low
This tool retrieves or queries data about a virtual machine without creating, modifying, deleting, or executing any operations. It is a read-only action that returns information about an existing VM identified by numeric ID, consistent with the 'Read' category for data retrieval operations with no side effects.
From the tool's definition Tool name 'vm_get' and description 'Get detailed information about a specific VM by its numeric ID' clearly indicate a retrieval operation with no modification of system state.
Attacks that exploit this kind of access
The rule that runs vm_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vm_get, this is the rule to start with:
vm_get 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 Truenas, apply this rule, and every vm_get call is checked against it from then on.
Questions about vm_get
Get detailed information about a specific VM by its numeric ID. It is categorised as a Read tool in the Truenas MCP Server, which means it retrieves data without modifying state.
Register the Truenas MCP server in PolicyLayer and add a rule for vm_get: 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 Truenas. Nothing to install.
vm_get 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_get 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_get. 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_get is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Truenas, and thousands of servers like it.
This server
Across the catalogue