Open native file picker dialog
AI agents use select_file to create or update resources in Apple Notifier — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Notifier environment.
An AI agent can call select_file faster than any human can review — one bad instruction and it creates or modifies resources in Apple Notifier by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Open native file picker dialog. It is categorised as a Write tool in the Apple Notifier MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apple Notifier MCP server in PolicyLayer and add a rule for select_file: 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 Apple Notifier. Nothing to install.
select_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the select_file 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.
Set action: deny in the PolicyLayer policy for select_file. 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.
select_file is provided by the Apple Notifier MCP server (piatra-automation/apple-notifier-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →