simctl_push_notification · Simctl MCP: Risk & Policy

WHAT IT DOES

What simctl_push_notification does on Simctl

AI agents invoke simctl_push_notification to trigger actions in Simctl. 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 simctl_push_notification needs a policy

Based on the tool name and server context (xcrun simctl commands for iOS Simulator), this tool likely sends push notifications to a simulated device. Push notifications trigger external operations and app behaviors on the simulator, placing this in the Execute category. Confidence is reduced due to the empty description.

From the tool's definition Tool name: simctl_push_notification; description is empty/uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simctl_push_notification Rate-limited

simctl_push_notification 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": {
    "simctl_push_notification": {
      "limits": [
        {
          "counter": "simctl_push_notification_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 Simctl, so you can run agents against it safely.

FAQ

Questions about simctl_push_notification

What does the simctl_push_notification tool do? +

simctl_push_notification. It is categorised as a Execute tool in the Simctl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on simctl_push_notification? +

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

What risk level is simctl_push_notification? +

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

Can I rate-limit simctl_push_notification? +

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

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

simctl_push_notification is provided by the Simctl MCP server (nzrsky/simctl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.