move_resize_window

THE RISK

Medium Risk

Why move_resize_window needs a policy

This tool modifies the state of an existing window (position and size) and may alter its maximized state. These changes are reversible (the window can be moved/resized back), so this falls under Write rather than Destructive. Misuse could disrupt the user's desktop layout or hide windows, giving it medium severity.

From the tool's definition Move and resize a window. Unmaximizes first if needed.

Documented attack patterns abuse exactly the kind of access move_resize_window gives an agent:

POLICY

How to control move_resize_window

PolicyLayer is an MCP gateway — it sits between your AI agents and GNOME Desktop MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for move_resize_window:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_resize_window": {
      "limits": [
        {
          "counter": "move_resize_window_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

move_resize_window stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register GNOME Desktop MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GNOME Desktop MCP tools

Destructive cleanup_screenshots Remove all temporary screenshot files. Destructive close_window Close a window. Execute activate_workspace Switch to a workspace by index (0-based). Execute focus_window Focus and raise a window. Execute key_combo Press a key combination. Execute key_press Press and release a single key. Execute minimize_window Minimize a window. Execute mouse_click Click at screen coordinates. button: 1=left, 2=middle, 3=right.

All 30 GNOME Desktop MCP tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about move_resize_window

What does the move_resize_window tool do? +

Move and resize a window. Unmaximizes first if needed. It is categorised as a Write tool in the GNOME Desktop MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_resize_window? +

Register the GNOME Desktop MCP server in PolicyLayer and add a rule for move_resize_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 GNOME Desktop MCP. Nothing to install.

What risk level is move_resize_window? +

move_resize_window is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit move_resize_window? +

Yes. Add a rate_limit block to the move_resize_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.

How do I block move_resize_window completely? +

Set action: deny in the PolicyLayer policy for move_resize_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.

What MCP server provides move_resize_window? +

move_resize_window is provided by the GNOME Desktop MCP server (sbuysse/gnome-desktop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GNOME Desktop MCP tool call.

Start from GNOME Desktop MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →