browser_click · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What browser_click does on LocalAnt

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

Browser click actions are Execute-category because their effects depend entirely on what element is targeted. A misused agent could click payment buttons, confirm dialogs, delete buttons on web apps, or trigger OAuth flows. Severity is high due to the broad blast radius across any web application the browser is open to.

From the tool's definition Click an element by selector — triggers a browser UI interaction that can submit forms, trigger purchases, navigate pages, or activate arbitrary web functionality depending on the element targeted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_click Rate-limited

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

FAQ

Questions about browser_click

What does the browser_click tool do? +

Click an element by selector. It is categorised as a Execute tool in the LocalAnt 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? +

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

What risk level is browser_click? +

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

Can I rate-limit browser_click? +

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

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

browser_click is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.