delete_photos
Delete photos by local identifier. Shows macOS confirmation dialog for user approval. Requires macOS 26+ Swift bridge.
This record as markdown: /tools/heznpc-airmcp/delete-photos.md
What delete_photos does on AirMCP
AI agents call delete_photos to permanently remove resources in AirMCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_photos is rated Critical
This tool deletes data that cannot be recovered without external backup restoration. Although a confirmation dialog provides a UX safeguard, the underlying operation is destructive and irreversible.
From the tool's definition "Delete photos by local identifier" — irreversibly removes photos from the user's library. The tool performs permanent deletion of media assets.
Attacks that exploit this kind of access
The rule that runs delete_photos safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_photos, this is the rule to start with:
delete_photos is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every delete_photos call is checked against it from then on.
Questions about delete_photos
Delete photos by local identifier. Shows macOS confirmation dialog for user approval. Requires macOS 26+ Swift bridge. It is categorised as a Destructive tool in the AirMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Air MCP server in PolicyLayer and add a rule for delete_photos: 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.
delete_photos is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_photos 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 delete_photos. 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.
delete_photos 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.
Across the catalogue