simulator_openurl · Xclaude Plugin MCP: Risk & Policy

WHAT IT DOES

What simulator_openurl does on Xclaude Plugin

AI agents invoke simulator_openurl to trigger actions in Xclaude Plugin. 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 simulator_openurl needs a policy

Opening a URL or deep link triggers external operations in the simulator — it can launch apps, navigate to content, or invoke deep link handlers. This is an execution action with side effects that depend on the URL argument, rather than a simple read or write operation.

From the tool's definition Open URL or deep link in simulator

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulator_openurl Rate-limited

simulator_openurl 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": {
    "simulator_openurl": {
      "limits": [
        {
          "counter": "simulator_openurl_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 Xclaude Plugin, so you can run agents against it safely.

FAQ

Questions about simulator_openurl

What does the simulator_openurl tool do? +

Open URL or deep link in simulator. It is categorised as a Execute tool in the Xclaude Plugin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on simulator_openurl? +

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

What risk level is simulator_openurl? +

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

Can I rate-limit simulator_openurl? +

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

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

simulator_openurl is provided by the Xclaude Plugin MCP server (conorluddy/xclaude-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

simulator_openurl is one line of Xclaude Plugin's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →