// MCP TOOL REFERENCE

click_element

Click the element with the specified index. Args: index (int): The index of the element to click Returns: str: A message describing the result of the click action

ServerMcp Browser Use
CategoryExecute

How to control click_element ↓

WHAT CLICK_ELEMENT ON MCP BROWSER USE DOES

AI agents invoke click_element to trigger actions in Mcp Browser Use. 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.

THE RISK

High Risk

Clicking browser elements can trigger a wide range of external operations: submitting forms, initiating downloads, navigating pages, activating purchases, or executing JavaScript handlers. The effect is entirely argument-dependent and can cascade into destructive or financial operations, making Execute the appropriate category at high severity.

From the tool's definition Click the element with the specified index — triggers browser click actions whose effects depend entirely on what element is clicked (form submissions, navigation, UI state changes, etc.)

Documented attack patterns abuse exactly the kind of access click_element gives an agent:

HOW TO CONTROL CLICK_ELEMENT

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Browser Use, and nothing reaches the server without passing your rules. This is the rule we recommend for click_element:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "click_element": {
      "limits": [
        {
          "counter": "click_element_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register Mcp Browser Use — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More Mcp Browser Use tools

Execute initialize_browser Initialize a new browser instance. Args: headless: Whether to run browser in h Execute wait Wait for the specified number of seconds. Args: seconds (int, optional): Numbe Execute search_google Search the query in Google in the current tab. Args: query (str): The search q Execute go_back Go back to the previous page. Returns: str: A message confirming navigation ba Execute go_to_url Navigate to URL in the current tab. Args: url (str): The URL to navigate to Execute input_text Input text into an interactive element at the specified index. Args: index (in Execute open_tab Open a URL in a new tab. Args: url (str): The URL to open in the new tab R Execute scroll_down Scroll down the page by the specified amount. Args: amount (int, optional): Pi

All 19 Mcp Browser Use tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Mcp Browser Use → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the click_element tool do? +

Click the element with the specified index. Args: index (int): The index of the element to click Returns: str: A message describing the result of the click action. It is categorised as a Execute tool in the Mcp Browser Use 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_element? +

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

What risk level is click_element? +

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

Can I rate-limit click_element? +

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

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

click_element is provided by the Mcp Browser Use MCP server (vinayak-mehta/mcp-browser-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Browser Use tool call.

Deterministic rules across all 19 Mcp Browser Use tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN MCP BROWSER USE →

Free to start. No card required.

19 Mcp Browser Use tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

click_element

// WHAT CLICK_ELEMENT ON MCP BROWSER USE DOES

// THE RISK

// HOW TO CONTROL CLICK_ELEMENT

// EXPLORE