mouse_move

Move the real mouse cursor to screen coordinates.

SERVERAgent Browser SOURCE335234131/agent-browser-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/335234131-agent-browser-mcp/mouse-move.md

WHAT IT DOES

What mouse_move does on Agent Browser

AI agents invoke mouse_move to trigger actions in Agent Browser. 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.

RISK

Why mouse_move is rated High

This tool performs physical mouse movement on the actual system, which is an external operation that triggers real browser/desktop interaction. While a move alone has limited blast radius, it enables agent-controlled UI interaction on the live system with real sessions/cookies.

From the tool's definition Move the real mouse cursor to screen coordinates

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mouse_move safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Browser, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mouse_move, this is the rule to start with:

mouse_move Rate-limited

mouse_move 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_move": {
      "limits": [
        {
          "counter": "mouse_move_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 Agent Browser, apply this rule, and every mouse_move call is checked against it from then on.

FAQ

Questions about mouse_move

What does the mouse_move tool do? +

Move the real mouse cursor to screen coordinates. It is categorised as a Execute tool in the Agent Browser 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_move? +

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

What risk level is mouse_move? +

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

Can I rate-limit mouse_move? +

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

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

mouse_move is provided by the Agent Browser MCP server (335234131/agent-browser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agent Browser, and thousands of servers like it.

This server

All 20 Agent Browser tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

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