browser_click_percent · DevLab MCP Suite MCP: Risk & Policy

WHAT IT DOES

What browser_click_percent does on DevLab MCP Suite

AI agents invoke browser_click_percent to trigger actions in DevLab MCP Suite. 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 browser_click_percent needs a policy

This tool performs a browser click action, which triggers external UI interactions in a browser or canvas game environment. Clicking can invoke arbitrary application logic (e.g., purchases, confirmations, game actions), making it an Execute-category tool. Misuse by an AI agent could trigger unintended UI actions, hence medium severity.

From the tool's definition Click using viewport-relative percentage coordinates. Ideal for canvas games.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_click_percent Rate-limited

browser_click_percent 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": {
    "browser_click_percent": {
      "limits": [
        {
          "counter": "browser_click_percent_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 DevLab MCP Suite, so you can run agents against it safely.

FAQ

Questions about browser_click_percent

What does the browser_click_percent tool do? +

Click using viewport-relative percentage coordinates. Ideal for canvas games. It is categorised as a Execute tool in the DevLab MCP Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_click_percent? +

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

What risk level is browser_click_percent? +

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

Can I rate-limit browser_click_percent? +

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

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

browser_click_percent is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.