permissions_status

SERVERLocal SOURCElocal-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/permissions-status.md

WHAT IT DOES

What permissions_status does on Local

AI agents call permissions_status to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why permissions_status is rated Low

This tool only reads and reports the current state of macOS TCC (Transparency, Consent, and Control) permissions. It has no side effects, does not modify system settings, execute code, or delete data. The blast radius of misuse is minimal—an AI agent could only learn which permissions are granted, which is read-only information useful for operational decision-making before other tools run.

From the tool's definition Tool 'Reports the TCC permission state' and 'Call it before a capture/automation run' — it retrieves and reports status information about system permissions without modifying, executing, or deleting anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs permissions_status safely

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

permissions_status Allowed

permissions_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "permissions_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about permissions_status

What does the permissions_status tool do? +

Reports the TCC permission state (screen recording, accessibility, microphone) this app needs to capture the screen and drive other apps' UI. Call it before a capture/automation run and surface the grant hints instead of failing mid-sequence. Screen Recording / Accessibility are granted in System Settings (not a JIT dialog); the URLs open the exact pane. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on permissions_status? +

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

What risk level is permissions_status? +

permissions_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit permissions_status? +

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

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

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

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →