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.

SERVERAirMCP SOURCEairmcp
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/heznpc-airmcp/setup-permissions.md

What setup_permissions does on AirMCP

AI agents invoke setup_permissions to trigger actions in AirMCP. 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 setup_permissions is rated High

This tool triggers system-level permission dialogs on macOS, which constitutes executing an external operation that modifies the system's permission state. While it doesn't delete data or move money, it actively changes OS-level access controls for multiple apps simultaneously. Misuse could grant broad permissions to unintended apps or be used to silently accept prompts in an automated context.

From the tool's definition "Trigger macOS permission prompts for all Apple apps used by AirMCP" and "Each app will show a one-time macOS permission dialog"

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 AirMCP 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 Air 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 AirMCP. 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 Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Air, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Air's. Pull the full record:

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.