window_manage · PC-Control MCP Server MCP: Risk & Policy

WHAT IT DOES

What window_manage does on PC-Control MCP Server

AI agents invoke window_manage to trigger actions in PC-Control 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.

WHY IT NEEDS A POLICY

Why window_manage needs a policy

Window management involves triggering external operations such as minimizing, maximizing, closing, resizing, or moving application windows. Closing a window could cause unsaved data loss (borderline Destructive), but the general case is Execute-level since effects are typically reversible.

From the tool's definition 'Manage a specific window' on a server that enables 'controlling windows and processes' through Claude Desktop

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

window_manage Rate-limited

window_manage stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "window_manage": {
      "limits": [
        {
          "counter": "window_manage_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches PC-Control MCP Server, so you can run agents against it safely.

FAQ

Questions about window_manage

What does the window_manage tool do? +

Manage a specific window. It is categorised as a Execute tool in the PC-Control MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on window_manage? +

Register the PC-Control MCP Server MCP server in PolicyLayer and add a rule for window_manage: 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 PC-Control MCP Server. Nothing to install.

What risk level is window_manage? +

window_manage is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit window_manage? +

Yes. Add a rate_limit block to the window_manage 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 window_manage completely? +

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

window_manage is provided by the PC-Control MCP Server MCP server (krsnmlna1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.