open_url

Open a URL in Safari

SERVERIconnect SOURCEiconnect-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/open-url.md

WHAT IT DOES

What open_url does on Iconnect

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

RISK

Why open_url is rated High

Opening a URL causes Safari to perform a network request and render external content. This is a browser action with side effects (e.g., could trigger downloads, execute JavaScript, authenticate sessions, or phish the user), placing it in the Execute category rather than a simple Read operation.

From the tool's definition 'Open a URL in Safari' — triggers an external browser action that navigates Safari to an arbitrary URL

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs open_url safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For open_url, this is the rule to start with:

open_url Rate-limited

open_url 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": {
    "open_url": {
      "limits": [
        {
          "counter": "open_url_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every open_url call is checked against it from then on.

FAQ

Questions about open_url

What does the open_url tool do? +

Open a URL in Safari. It is categorised as a Execute tool in the Iconnect 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_url? +

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

What risk level is open_url? +

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

Can I rate-limit open_url? +

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

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

open_url is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →