AI agents use unmaximize_window to create or update resources in GNOME Desktop MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GNOME Desktop MCP environment.
This tool modifies the visual/layout state of a window by restoring it from maximized state. It is reversible (the window can be re-maximized), has no data destruction, financial, or code execution implications. Blast radius is low as it only affects window presentation on the desktop.
From the tool's definition 'Unmaximize a window' — changes the window state from maximized to restored/normal
Documented attack patterns abuse exactly the kind of access unmaximize_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 unmaximize_window:
{
"version": "1",
"default": "deny",
"tools": {
"unmaximize_window": {
"limits": [
{
"counter": "unmaximize_window_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}unmaximize_window stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Unmaximize a window. It is categorised as a Write tool in the GNOME Desktop MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GNOME Desktop MCP server in PolicyLayer and add a rule for unmaximize_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.
unmaximize_window 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 unmaximize_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 unmaximize_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.
unmaximize_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.