click_at_position · Gacha MCP: Risk & Policy

WHAT IT DOES

What click_at_position does on GachaMCP

AI agents invoke click_at_position to trigger actions in GachaMCP. 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_at_position needs a policy

This tool performs UI automation by clicking at specific coordinates within a game window. Clicks can trigger purchases, confirmations, in-game transactions (e.g., gacha pulls which may involve real or virtual currency), or other irreversible actions depending on where the click lands.

From the tool's definition 'click_at_position' - clicks at specific coordinates on the game window; part of a click automation system described in server description as 'click automation'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

click_at_position Rate-limited

click_at_position 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_at_position": {
      "limits": [
        {
          "counter": "click_at_position_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 GachaMCP, so you can run agents against it safely.

FAQ

Questions about click_at_position

What does the click_at_position tool do? +

Click tại tọa độ cụ thể trên cửa sổ game. It is categorised as a Execute tool in the GachaMCP 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_at_position? +

Register the Gacha MCP server in PolicyLayer and add a rule for click_at_position: 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 GachaMCP. Nothing to install.

What risk level is click_at_position? +

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

Can I rate-limit click_at_position? +

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

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

click_at_position is provided by the Gacha MCP server (nguyenhuynhphuvinh/gachamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.