Perform mouse clicks at precise screen coordinates with support for left, right, or middle mouse buttons. Essential for interacting with UI elements, buttons, menus, and any clickable interface components. Supports both single clicks and double-clicks. Use coordinates from screenshot analysis, fi...
AI agents invoke click 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.
Clicking UI elements triggers arbitrary external operations depending on what is clicked — submitting forms, opening applications, confirming dialogs, activating menus, etc. Effects are context-dependent and can be wide-ranging, making this an Execute-category tool with high severity since an AI agent could click destructive or sensitive UI controls (e.g., confirm delete, send message, approve transaction).
From the tool's definition Perform mouse clicks at precise screen coordinates... Essential for interacting with UI elements, buttons, menus, and any clickable interface components. Supports both single clicks and double-clicks.
Documented attack patterns abuse exactly the kind of access click 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 click:
{
"version": "1",
"default": "deny",
"tools": {
"click": {
"limits": [
{
"counter": "click_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Perform mouse clicks at precise screen coordinates with support for left, right, or middle mouse buttons. Essential for interacting with UI elements, buttons, menus, and any clickable interface components. Supports both single clicks and double-clicks. Use coordinates from screenshot analysis, find_text results, or window information. Always validate coordinates are within screen bounds using get_screen_info first. Consider using find_text to locate clickable text elements dynamically rather than hardcoded coordinates. Automatically moves mouse to target location before clicking. Requires accessibility permission on macOS. 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 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 macOS Simulator MCP Server. Nothing to install.
click 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 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.
Set action: deny in the PolicyLayer policy for 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.
click 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.