AI agents invoke fullscreen_window to trigger actions in MacWright. 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 triggers an external UI operation (toggling fullscreen mode) on a macOS application window. It modifies the display state of a running application without permanently destroying data, making it an Execute-level action. Misuse could disrupt an agent's ability to interact with the UI or interfere with other running applications, warranting medium severity.
From the tool's definition Toggle fullscreen mode for an application
Attacks that exploit this kind of access
Toggle fullscreen mode for an application. It is categorised as a Execute tool in the MacWright MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MacWright MCP server in PolicyLayer and add a rule for fullscreen_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 MacWright. Nothing to install.
fullscreen_window 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 fullscreen_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 fullscreen_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.
fullscreen_window is provided by the MacWright MCP server (ruchit-p/macwright). 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 →