tap_back

THE RISK

High Risk

Why tap_back needs a policy

This tool performs a touch interaction (tap) on a virtual iOS device, specifically triggering a UI navigation action. It executes an action on an external system (virtual machine), making it Execute category. The blast radius is low since it only navigates back in an app and does not modify or delete data.

From the tool's definition Tap the iOS navigation back button (top-left corner)

Documented attack patterns abuse exactly the kind of access tap_back gives an agent:

POLICY

How to control tap_back

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_back:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tap_back": {
      "limits": [
        {
          "counter": "tap_back_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

tap_back 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.

Create a free account and register Vphone — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Vphone tools

Execute go_home Press the home button to return to the home screen. Execute open_app Open an app from the home screen by name. Execute open_app_switcher Slow swipe up from bottom to open the App Switcher. Execute open_control_center Swipe down from the top-right to open Control Center. Execute open_notification_center Swipe down from the top-left to open Notification Center. Execute open_search Tap the Search bar on the home screen. Execute press_power Press the power button (lock/wake). Execute scroll_down Scroll down on the current screen.

All 17 Vphone tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Vphone → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about tap_back

What does the tap_back tool do? +

Tap the iOS navigation back button (top-left corner). 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.

How do I enforce a policy on tap_back? +

Register the Vphone MCP server in PolicyLayer and add a rule for tap_back: 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.

What risk level is tap_back? +

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

Can I rate-limit tap_back? +

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

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

tap_back 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.

Enforce policy on every Vphone tool call.

Start from Vphone, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →