xcode_push_notification_simulator · Xcode MCP: Risk & Policy

WHAT IT DOES

What xcode_push_notification_simulator does on Xcode

AI agents invoke xcode_push_notification_simulator to trigger actions in Xcode. 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.

WHY IT NEEDS A POLICY

Why xcode_push_notification_simulator needs a policy

This tool executes an action on a simulator by pushing a notification event, which is an external operation with effects dependent on the notification payload. It doesn't read, write persistent data, or delete anything, but it triggers runtime behavior in the simulator environment.

From the tool's definition 'Simulate a push notification on a simulator' — triggers an external operation (sending a push notification to a running simulator)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

xcode_push_notification_simulator Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Xcode, so you can run agents against it safely.

FAQ

Questions about xcode_push_notification_simulator

What does the xcode_push_notification_simulator tool do? +

Simulate a push notification on a simulator. It is categorised as a Execute tool in the Xcode MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on xcode_push_notification_simulator? +

Register the Xcode MCP server in PolicyLayer and add a rule for xcode_push_notification_simulator: 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 Xcode. Nothing to install.

What risk level is xcode_push_notification_simulator? +

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

Can I rate-limit xcode_push_notification_simulator? +

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

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

xcode_push_notification_simulator is provided by the Xcode MCP server (raunaksplanet/xcode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.