Returns the name of the current environment reported by the server.
AI agents call get_desktop_name to retrieve information from Vnc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs only information retrieval—it queries and returns a string identifier for the desktop environment. There is no data modification, code execution, destructive action, or financial operation. The blast radius of misuse is minimal, as an attacker could only learn the name of the environment they are already connected to.
From the tool's definition Tool name 'get_desktop_name' and description 'Returns the name of the current environment reported by the server' indicate a read-only query that retrieves metadata about the VNC session without side effects.
Documented attack patterns abuse exactly the kind of access get_desktop_name gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vnc, and nothing reaches the server without passing your rules. This is the rule we recommend for get_desktop_name:
{
"version": "1",
"default": "deny",
"tools": {
"get_desktop_name": {}
}
}get_desktop_name 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.
Returns the name of the current environment reported by the server. It is categorised as a Read tool in the Vnc MCP Server, which means it retrieves data without modifying state.
Register the Vnc MCP server in PolicyLayer and add a rule for get_desktop_name: 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. Nothing to install.
get_desktop_name 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_desktop_name 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_desktop_name. 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_desktop_name is provided by the Vnc MCP server (regulad/vnc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vnc, 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.
20 Vnc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.