Get detailed information about a specific VM.
AI agents call get_vm_info to retrieve information from VMware Fusion MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries VM metadata without modifying, executing, or destroying any resources. It matches the 'Read' category definition of retrieving or querying data with no side effects. Severity is low because exposure of VM information alone has limited blast radius, though it could inform further attacks if sensitive configuration details are exposed.
From the tool's definition Tool name is 'get_vm_info' and description states it 'Get detailed information about a specific VM.' This is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_vm_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VMware Fusion MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_vm_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_vm_info": {}
}
}get_vm_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a specific VM. It is categorised as a Read tool in the VMware Fusion MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VMware Fusion MCP Server MCP server in PolicyLayer and add a rule for get_vm_info: 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 VMware Fusion MCP Server. Nothing to install.
get_vm_info 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 get_vm_info 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 get_vm_info. 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.
get_vm_info is provided by the VMware Fusion MCP Server MCP server (yeahdongcn/vmware-fusion-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VMware Fusion MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 VMware Fusion MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.