Execute bulk create, update, and delete operations
AI agents call bulk_operations to permanently remove resources in Directus MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While the tool includes reversible operations (create, update), the inclusion of bulk delete operations pushes this into the Destructive category per severity hierarchy rules (Destructive > Execute > Write > Read). Bulk operations amplify risk—a single misuse could delete thousands of records irreversibly. High severity reflects the blast radius of accidental or malicious bulk deletions in a CMS context.
From the tool's definition Tool description explicitly states it can execute 'bulk create, update, and delete operations.' The delete component makes this destructive, as bulk deletions are irreversible and can wipe large datasets at once.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Execute bulk create, update, and delete operations. It is categorised as a Destructive tool in the Directus MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Directus MCP Server MCP server in PolicyLayer and add a rule for bulk_operations: 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 Directus MCP Server. Nothing to install.
bulk_operations 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_operations 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_operations. 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_operations is provided by the Directus MCP Server MCP server (staminna/mcp-server-claude). 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 →