Resize and/or move a window by title
AI agents invoke desktop_window_resize to trigger actions in MCP Desktop Tools. 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 performs desktop automation actions (resizing and moving windows) that constitute external operations on the system. While not destructive or data-modifying, it triggers real UI/window management operations. The blast radius is low since it only affects window positioning/sizing and is easily reversible, but it fits Execute as it interacts with the operating system's window management.
From the tool's definition Resize and/or move a window by title
Attacks that exploit this kind of access
Resize and/or move a window by title. It is categorised as a Execute tool in the MCP Desktop Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Desktop Tools MCP server in PolicyLayer and add a rule for desktop_window_resize: 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 MCP Desktop Tools. Nothing to install.
desktop_window_resize 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 desktop_window_resize 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 desktop_window_resize. 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.
desktop_window_resize is provided by the MCP Desktop Tools MCP server (k1ta141k/mcp-desktop-tools). 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 →