connect_window · Maa MCP: Risk & Policy

WHAT IT DOES

What connect_window does on MaaMCP

AI agents invoke connect_window to trigger actions in MaaMCP. 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 connect_window needs a policy

Based on the server context (Windows desktop automation) and sibling tools like 'find_window_list', 'click', 'connect_adb_device', this tool likely connects to or attaches to a Windows application window for automation. This constitutes an Execute-level action as it initiates an external operation (connecting to/controlling a window).

From the tool's definition Tool name 'connect_window' on a server providing Android and Windows desktop automation capabilities. Description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_window Rate-limited

connect_window 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": {
    "connect_window": {
      "limits": [
        {
          "counter": "connect_window_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 MaaMCP, so you can run agents against it safely.

FAQ

Questions about connect_window

What does the connect_window tool do? +

connect_window. It is categorised as a Execute tool in the MaaMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on connect_window? +

Register the Maa MCP server in PolicyLayer and add a rule for connect_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 MaaMCP. Nothing to install.

What risk level is connect_window? +

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

Can I rate-limit connect_window? +

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

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

connect_window is provided by the Maa MCP server (maa-ai/maamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.