Delete multiple items at once efficiently (max 20 items per request, implemented via sequential API calls)
AI agents call bulk_delete_items to permanently remove resources in Miro MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs bulk deletion of board items, which cannot be undone. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone'.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete multiple items at once efficiently'. This is an irreversible operation that removes data from Miro boards.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete multiple items at once efficiently (max 20 items per request, implemented via sequential API calls). It is categorised as a Destructive tool in the Miro MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Miro MCP Server MCP server in PolicyLayer and add a rule for bulk_delete_items: 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 Miro MCP Server. Nothing to install.
bulk_delete_items 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 bulk_delete_items 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 bulk_delete_items. 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.
bulk_delete_items is provided by the Miro MCP Server MCP server (soul-script/miro-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 →