AI agents invoke tap to trigger actions in Vphone. 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.
The 'tap' tool almost certainly simulates a touch/tap interaction on the iOS virtual machine's screen. This is an Execute-category action as it triggers UI interactions whose effects depend entirely on what is being tapped — it could open apps, confirm dialogs, submit forms, or trigger arbitrary in-app actions.
From the tool's definition Tool name 'tap' on a server that exposes 'touch input and navigation tools' and 'raw touch interactions' for iOS virtual machines
Documented attack patterns abuse exactly the kind of access tap gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vphone, and nothing reaches the server without passing your rules. This is the rule we recommend for tap:
{
"version": "1",
"default": "deny",
"tools": {
"tap": {
"limits": [
{
"counter": "tap_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}tap 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.
tap. It is categorised as a Execute tool in the Vphone MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vphone MCP server in PolicyLayer and add a rule for tap: 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 Vphone. Nothing to install.
tap 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 tap 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 tap. 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.
tap is provided by the Vphone MCP server (pluginslab/vphone-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vphone, 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.
17 Vphone tools catalogued and risk-classified — across an index of 43,000+ MCP servers.