setup_permissions

Trigger macOS permission prompts for all Apple apps used by AirMCP. Run this once after installation to grant all permissions at once. Each app will show a one-time macOS permission dialog.

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/setup-permissions.md

WHAT IT DOES

What setup_permissions does on Iconnect

AI agents invoke setup_permissions 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 setup_permissions is rated High

This tool triggers OS-level permission prompts and grants access to multiple Apple ecosystem apps. It's an external operation that modifies system permission state. While not purely destructive or financial, it executes system-level actions (triggering macOS dialogs, granting permissions) that have real side effects on the security posture of the machine.

From the tool's definition 'Trigger macOS permission prompts for all Apple apps used by AirMCP' — actively triggers system-level permission dialogs and grants permissions across multiple Apple apps

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs setup_permissions 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 setup_permissions, this is the rule to start with:

setup_permissions Rate-limited

setup_permissions 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": {
    "setup_permissions": {
      "limits": [
        {
          "counter": "setup_permissions_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 setup_permissions call is checked against it from then on.

FAQ

Questions about setup_permissions

What does the setup_permissions tool do? +

Trigger macOS permission prompts for all Apple apps used by AirMCP. Run this once after installation to grant all permissions at once. Each app will show a one-time macOS permission dialog. 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 setup_permissions? +

Register the Iconnect MCP server in PolicyLayer and add a rule for setup_permissions: 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 setup_permissions? +

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

Can I rate-limit setup_permissions? +

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

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

setup_permissions 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 →