web_click

SERVERLocal SOURCElocal-mcp

High RISK CLASS

Category Execute

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/web-click.md

WHAT IT DOES

What web_click does on Local

AI agents invoke web_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
`target`	string	Yes	CSS selector or visible text of the element to click.
`confirm`	boolean	—	Required (true) to perform a click that submits a form.
`session`	string	—	Session name (default 'default').

Parameters from the server's own tool schema.

RISK

Why web_click is rated High

This tool performs browser click actions that can trigger arbitrary web interactions including form submissions, button presses, and navigation. The effects are highly context-dependent — a misused click could submit forms, trigger purchases, send messages, or initiate other irreversible web-based actions.

From the tool's definition Clicks an element on the current page... Clicks that SUBMIT a form preview first — call again with confirm:true to execute; plain links/buttons click directly

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs web_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 web_click, this is the rule to start with:

web_click Rate-limited

web_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": {
    "web_click": {
      "limits": [
        {
          "counter": "web_click_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every web_click call is checked against it from then on.

FAQ

Questions about web_click

What does the web_click tool do? +

Clicks an element on the current page. target is a CSS selector or visible text (resolved fresh each call). Clicks that SUBMIT a form preview first — call again with confirm:true to execute; plain links/buttons click directly. Returns the resulting URL/title. 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.

What parameters does web_click accept? +

web_click accepts 3 parameters: target, confirm, session. Required: target. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on web_click? +

Register the Local MCP server in PolicyLayer and add a rule for web_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.

What risk level is web_click? +

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

Can I rate-limit web_click? +

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

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

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

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server →qt_click on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →