mouse_click_at · Chrome Extension MCP Bridge MCP

WHAT IT DOES

What mouse_click_at does on Chrome Extension MCP Bridge

AI agents invoke mouse_click_at to trigger actions in Chrome Extension MCP Bridge. 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 mouse_click_at needs a policy

Clicking at arbitrary coordinates can trigger any interactive element on a page (buttons, links, form submissions, purchases, deletes), making this an Execute-category tool with high severity since an AI agent could misuse it to interact with sensitive UI elements unpredictably.

From the tool's definition 'Click at specific x,y pixel coordinates on the page' — triggers a browser click action at arbitrary coordinates, causing external browser interactions whose effects depend on what element is at those coordinates.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mouse_click_at Rate-limited

mouse_click_at 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": {
    "mouse_click_at": {
      "limits": [
        {
          "counter": "mouse_click_at_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 Chrome Extension MCP Bridge, so you can run agents against it safely.

FAQ

Questions about mouse_click_at

What does the mouse_click_at tool do? +

Click at specific x,y pixel coordinates on the page. It is categorised as a Execute tool in the Chrome Extension MCP Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mouse_click_at? +

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

What risk level is mouse_click_at? +

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

Can I rate-limit mouse_click_at? +

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

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

mouse_click_at is provided by the Chrome Extension MCP Bridge MCP server (ivoglent/chrome-mcp-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.