open_control_center

THE RISK

High Risk

Why open_control_center needs a policy

This tool triggers a physical gesture/navigation action on an iOS virtual machine (a swipe interaction), which is an external operation that affects the device's UI state. It doesn't read data, write/modify stored data, or destroy anything — it executes a touch/navigation action on the device.

From the tool's definition Swipe down from the top-right to open Control Center

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

POLICY

How to control open_control_center

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

policy.json

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

open_control_center 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_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. Execute scroll_up Scroll up 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 open_control_center

What does the open_control_center tool do? +

Swipe down from the top-right to open Control Center. 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 open_control_center? +

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

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

Can I rate-limit open_control_center? +

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

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

open_control_center 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 →