Move a window to a specific position for precise control
AI agents invoke set_window_position 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 triggers an external operation on the macOS windowing system — repositioning a window. It's not a simple data read/write but an action that manipulates the UI/OS environment, making it Execute. Misuse could disrupt user workflows by moving windows unexpectedly, but it's reversible and limited in blast radius.
From the tool's definition Move a window to a specific position for precise control
Attacks that exploit this kind of access
Move a window to a specific position for precise control. 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 set_window_position: 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.
set_window_position 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 set_window_position 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 set_window_position. 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.
set_window_position 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 →