chrome_click
Clicks the first element matching a CSS selector in the current Google Chrome tab. Returns the tag name and visible text of the clicked element so you can confirm the right thing was hit. Pass wait_for_navigation: true to wait up to 3 seconds for the page to load after the click.
This record as markdown: /tools/com-local-mcp-local-mcp/chrome-click.md
What chrome_click does on Local
AI agents invoke chrome_click to trigger actions in Local. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
nth | integer | — | Which match to click if there are several (0-based, default 0) |
selector | string | Yes | CSS selector (e.g. 'button.primary', '#save', '[data-testid=login]') |
wait_for_navigation | boolean | — | Wait up to 3s for page load after click (default false) |
Parameters from the server's own tool schema.
Why chrome_click is rated High
Clicking a UI element triggers external browser actions whose effects depend on what element is clicked — could submit forms, trigger purchases, delete content, navigate to pages, or activate any interactive element. This is a browser automation action that executes real interactions with unpredictable side effects depending on the target element.
From the tool's definition Clicks the first element matching a CSS selector in the current Google Chrome tab
Attacks that exploit this kind of access
The rule that runs chrome_click safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chrome_click, this is the rule to start with:
chrome_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every chrome_click call is checked against it from then on.
Questions about chrome_click
Clicks the first element matching a CSS selector in the current Google Chrome tab. Returns the tag name and visible text of the clicked element so you can confirm the right thing was hit. Pass wait_for_navigation: true to wait up to 3 seconds for the page to load after the click. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
chrome_click accepts 3 parameters: nth, selector, wait_for_navigation. Required: selector. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for chrome_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 Local. Nothing to install.
chrome_click is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the chrome_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.
Set action: deny in the PolicyLayer policy for chrome_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.
chrome_click is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
Across the catalogue