AI agents call get_window to retrieve information from GNOME Desktop MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns window properties without modifying, executing, deleting, or controlling the window itself. It is a passive information retrieval operation. The broader server context includes Execute and Write tools (key_press, mouse injection, window management), but this specific tool performs only read operations. Severity is low because window metadata disclosure poses minimal immediate risk.
From the tool's definition Tool name 'get_window' and description 'Get detailed properties of a specific window' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_window gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GNOME Desktop MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_window:
{
"version": "1",
"default": "deny",
"tools": {
"get_window": {}
}
}get_window 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 properties of a specific window. It is categorised as a Read tool in the GNOME Desktop MCP MCP Server, which means it retrieves data without modifying state.
Register the GNOME Desktop MCP server in PolicyLayer and add a rule for get_window: 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 GNOME Desktop MCP. Nothing to install.
get_window 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_window 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_window. 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_window is provided by the GNOME Desktop MCP server (sbuysse/gnome-desktop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GNOME Desktop MCP, 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.
30 GNOME Desktop MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.