This record as markdown: /tools/io-github-0nork-0nmcp/crm-media-bulk-delete.md
What crm_media_bulk_delete does on 0nmcp
AI agents call crm_media_bulk_delete to permanently remove resources in 0nmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why crm_media_bulk_delete is rated Critical
This tool performs bulk deletion of files and folders, which is an irreversible destructive action. Even if items are moved to trash rather than permanently deleted, bulk operations on user data have a high blast radius if invoked incorrectly by an AI agent (e.g., deleting the wrong set of records or all records when only a subset should be removed).
From the tool's definition 'Bulk delete or trash multiple files and folders' — the verb 'delete' combined with 'bulk' operation on 'multiple files and folders' indicates irreversible removal of data at scale.
Attacks that exploit this kind of access
The rule that runs crm_media_bulk_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_media_bulk_delete, this is the rule to start with:
crm_media_bulk_delete 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 0nmcp, apply this rule, and every crm_media_bulk_delete call is checked against it from then on.
Questions about crm_media_bulk_delete
Bulk delete or trash multiple files and folders. It is categorised as a Destructive tool in the 0nmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 0n MCP server in PolicyLayer and add a rule for crm_media_bulk_delete: 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 0nmcp. Nothing to install.
crm_media_bulk_delete 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 crm_media_bulk_delete 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 crm_media_bulk_delete. 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.
crm_media_bulk_delete is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
Across the catalogue