Create a quad (2x2) window layout on a specific display
AI agents invoke create_quad_layout to trigger actions in Moom MCP Server. 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 executes programmatic window layout operations on macOS, repositioning and resizing multiple application windows into a 2x2 grid. It triggers external operations (via Moom) whose effects depend on arguments (which display, which windows). While reversible in principle, it's an Execute-class action as it manipulates the OS window environment.
From the tool's definition Create a quad (2x2) window layout on a specific display — triggers external window management operations that rearrange application windows on the display
Attacks that exploit this kind of access
Create a quad (2x2) window layout on a specific display. It is categorised as a Execute tool in the Moom MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Moom MCP Server MCP server in PolicyLayer and add a rule for create_quad_layout: 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 Moom MCP Server. Nothing to install.
create_quad_layout 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 create_quad_layout 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 create_quad_layout. 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.
create_quad_layout is provided by the Moom MCP Server MCP server (itrimble/moom-mcp). 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 →