Launch a GUI application on the remote desktop (Linux focus)
AI agents invoke vnc_launch_gui_app to trigger actions in VNC MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool enables execution of arbitrary GUI applications on a remote desktop system. While not immediately destructive, the ability to launch any application represents a high-severity Execute risk because: (1) it can trigger side effects depending on which application is launched and its configuration; (2) a compromised or misaligned AI agent could launch malicious applications, privilege escalation tools, or…
From the tool's definition Tool description states "Launch a GUI application on the remote desktop", which constitutes executing arbitrary applications on a remote system.
Attacks that exploit this kind of access
Launch a GUI application on the remote desktop (Linux focus). It is categorised as a Execute tool in the VNC MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the VNC MCP Server MCP server in PolicyLayer and add a rule for vnc_launch_gui_app: 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_launch_gui_app is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vnc_launch_gui_app 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_launch_gui_app. 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_launch_gui_app 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 →