Verifies if a port is listening in the VM and optionally accessible from the host. Differentiates
AI agents call check_vm_port to retrieve information from Virtualbox MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about port listening status without side effects. It performs a read-only verification check against VM network state. No data is modified, deleted, or executed. The blast radius of misuse is minimal—an agent could only perform unnecessary checks or discover open ports, neither of which causes harm.
From the tool's definition Tool name 'check_vm_port' and description 'Verifies if a port is listening' indicate a query/inspection operation. The action is checking/monitoring state, not modifying or executing code.
Attacks that exploit this kind of access
Verifies if a port is listening in the VM and optionally accessible from the host. Differentiates. It is categorised as a Read tool in the Virtualbox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Virtualbox MCP Server MCP server in PolicyLayer and add a rule for check_vm_port: 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 Virtualbox MCP Server. Nothing to install.
check_vm_port 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 check_vm_port 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 check_vm_port. 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.
check_vm_port is provided by the Virtualbox MCP Server MCP server (usemanusai/virtualbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →