AI agents invoke iphone_operate_click to trigger actions in iPhone 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 executes a UI interaction (tap/click) on a live iPhone device. Its effects depend entirely on what element is tapped — it could open apps, confirm dialogs, submit forms, or trigger purchases. This makes it an Execute-category tool with medium severity, as misuse could trigger unintended actions but consequences vary widely by context.
From the tool's definition 'Perform tap' — triggers a touch/click action on the iPhone UI via Appium automation
Documented attack patterns abuse exactly the kind of access iphone_operate_click gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and iPhone MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for iphone_operate_click:
{
"version": "1",
"default": "deny",
"tools": {
"iphone_operate_click": {
"limits": [
{
"counter": "iphone_operate_click_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}iphone_operate_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 tap. It is categorised as a Execute tool in the iPhone MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the iPhone MCP Server MCP server in PolicyLayer and add a rule for iphone_operate_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 iPhone MCP Server. Nothing to install.
iphone_operate_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 iphone_operate_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 iphone_operate_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.
iphone_operate_click is provided by the iPhone MCP Server MCP server (lakr233/iphone-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from iPhone 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.
9 iPhone MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.