window_fullscreen
Toggle fullscreen (real) or maximized (fake). Defaults to the focused window; pass address/match for an explicit target.
This record as markdown: /tools/omarchy-mcp/window-fullscreen.md
What window_fullscreen does on Omarchy-MCP
AI agents invoke window_fullscreen to trigger actions in Omarchy-MCP. 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.
Why window_fullscreen is rated High
Triggers window state change on desktop, affecting display of running applications.
From the tool's definition Toggle fullscreen... focused window... explicit target
Attacks that exploit this kind of access
The rule that runs window_fullscreen safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Omarchy-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For window_fullscreen, this is the rule to start with:
window_fullscreen stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Omarchy-MCP, apply this rule, and every window_fullscreen call is checked against it from then on.
Questions about window_fullscreen
Toggle fullscreen (real) or maximized (fake). Defaults to the focused window; pass address/match for an explicit target. It is categorised as a Execute tool in the Omarchy-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Omarchy MCP server in PolicyLayer and add a rule for window_fullscreen: 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 Omarchy-MCP. Nothing to install.
window_fullscreen 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 window_fullscreen 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 window_fullscreen. 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.
window_fullscreen is provided by the Omarchy MCP server (hlsitechio/Omarchy-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Omarchy, and thousands of servers like it.
Across the catalogue