browserbeam_click · Browserbeam MCP Server MCP

WHAT IT DOES

What browserbeam_click does on Browserbeam MCP Server

AI agents invoke browserbeam_click to trigger actions in Browserbeam MCP Server. 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 browserbeam_click needs a policy

Clicking elements in a browser can trigger arbitrary external operations: form submissions, purchases, deletions, navigation, API calls, etc. The effect depends entirely on what element is clicked, making this an Execute-category action with high blast radius since an AI agent could click destructive or financial action buttons.

From the tool's definition 'Click an element on the page' — triggers browser interaction/action on a live web page

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browserbeam_click Rate-limited

browserbeam_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": {
    "browserbeam_click": {
      "limits": [
        {
          "counter": "browserbeam_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 Browserbeam MCP Server, so you can run agents against it safely.

FAQ

Questions about browserbeam_click

What does the browserbeam_click tool do? +

Click an element on the page. Use ref (e.g. It is categorised as a Execute tool in the Browserbeam MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browserbeam_click? +

Register the Browserbeam MCP Server MCP server in PolicyLayer and add a rule for browserbeam_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 Browserbeam MCP Server. Nothing to install.

What risk level is browserbeam_click? +

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

Can I rate-limit browserbeam_click? +

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

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

browserbeam_click is provided by the Browserbeam MCP Server MCP server (nyku/browserbeam-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.