High Risk →

open_notification_center

Swipe down from the top-left to open Notification Center.

How to control open_notification_center ↓

What open_notification_center does on Vphone

AI agents invoke open_notification_center 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.

High Risk

Why open_notification_center needs a policy

This tool triggers a UI gesture (swipe) on the virtual iOS device to open the Notification Center. It executes an input/navigation action on an external system (the virtual machine), consistent with the Execute category. Blast radius is low as it only opens a system panel and doesn't modify or delete data.

From the tool's definition Swipe down from the top-left to open Notification Center

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

How to control open_notification_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_notification_center:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "open_notification_center": {
      "limits": [
        {
          "counter": "open_notification_center_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Vphone — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about open_notification_center

What does the open_notification_center tool do? +

Swipe down from the top-left to open Notification 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_notification_center? +

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

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

Can I rate-limit open_notification_center? +

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

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

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

Free to start. No card required.

17 Vphone tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.