Disconnect from the VNC server
AI agents use vnc_disconnect to create or update resources in VNC MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VNC MCP Server environment.
An AI agent can call vnc_disconnect faster than any human can review — one bad instruction and it creates or modifies resources in VNC MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Disconnect from the VNC server. It is categorised as a Write tool in the VNC MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VNC MCP Server MCP server in PolicyLayer and add a rule for vnc_disconnect: 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 VNC MCP Server. Nothing to install.
vnc_disconnect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vnc_disconnect 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 vnc_disconnect. 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.
vnc_disconnect is provided by the VNC MCP Server MCP server (volkan-m/vnc-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 →