New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

browser_mouse_move

A execute tool on the Termux Browser Pilot MCP server.

SERVERTermux Browser Pilot SOURCEsalviz/termux-browser-pilot
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/salviz-termux-browser-pilot/browser-mouse-move.md

What browser_mouse_move does on Termux Browser Pilot

AI agents invoke browser_mouse_move to trigger actions in Termux Browser Pilot. 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 browser_mouse_move is rated High

Based on the tool name, this tool moves the mouse cursor within a browser automation context. Mouse movement is a browser action/interaction that can trigger UI events (hover effects, tooltips, dynamic content). It is part of a real browser automation system running Firefox/Chromium. While moving the mouse alone has limited blast radius, it can be chained with other actions to perform unintended interactions.

From the tool's definition Tool name 'browser_mouse_move' on a browser automation server; description is empty and uninformative.

Questions about browser_mouse_move

What does the browser_mouse_move tool do? +

browser_mouse_move is a execute tool on the Termux Browser Pilot MCP server. It is categorised as a Execute tool in the Termux Browser Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_mouse_move? +

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

What risk level is browser_mouse_move? +

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

Can I rate-limit browser_mouse_move? +

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

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

browser_mouse_move is provided by the Termux Browser Pilot MCP server (salviz/termux-browser-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Termux Browser Pilot, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Termux Browser Pilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.