Move the mouse cursor to precise screen coordinates without clicking. Useful for hover actions, preparing for subsequent clicks, or triggering hover-based UI elements like tooltips and menus. Supports smooth movement animation (default) or instant positioning. Often used before click operations o...
AI agents invoke mouse_move to trigger actions in macOS Simulator MCP Server. 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.
This tool controls the mouse cursor on the host macOS system, which constitutes an external operation/browser-like action affecting the UI state. While it doesn't click, it can trigger hover-based UI interactions and reveal hidden elements, making it an Execute-category tool. Misuse could manipulate UI state or prepare for subsequent harmful actions.
From the tool's definition Move the mouse cursor to precise screen coordinates without clicking... triggering hover-based UI elements like tooltips and menus... reveal hidden UI elements that appear on hover
Documented attack patterns abuse exactly the kind of access mouse_move gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and macOS Simulator MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mouse_move:
{
"version": "1",
"default": "deny",
"tools": {
"mouse_move": {
"limits": [
{
"counter": "mouse_move_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Move the mouse cursor to precise screen coordinates without clicking. Useful for hover actions, preparing for subsequent clicks, or triggering hover-based UI elements like tooltips and menus. Supports smooth movement animation (default) or instant positioning. Often used before click operations or to reveal hidden UI elements that appear on hover. Validate coordinates with get_screen_info to ensure they. It is categorised as a Execute tool in the macOS Simulator MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the macOS Simulator MCP Server 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 macOS Simulator MCP Server. Nothing to install.
mouse_move 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 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.
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.
mouse_move is provided by the macOS Simulator MCP Server MCP server (ohqay/mac-commander). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from macOS Simulator MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 macOS Simulator MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.