click_key · Maa MCP: Risk & Policy

WHAT IT DOES

What click_key does on MaaMCP

AI agents invoke click_key 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 click_key needs a policy

The tool name 'click_key' strongly implies simulating a key press or click action on an Android device or Windows desktop, which constitutes executing an action on an external system. The description is empty, lowering confidence, but context from sibling tools and server description supports an Execute classification. Misuse could trigger unintended operations on automated devices.

From the tool's definition Tool name 'click_key' on a server providing Android device and Windows desktop automation; sibling tools include 'click', 'double_click', suggesting UI interaction/execution capabilities

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

click_key Rate-limited

click_key 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": {
    "click_key": {
      "limits": [
        {
          "counter": "click_key_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 click_key

What does the click_key tool do? +

click_key. 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 click_key? +

Register the Maa MCP server in PolicyLayer and add a rule for click_key: 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 click_key? +

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

Can I rate-limit click_key? +

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

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

click_key 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.