delete_operations

Delete multiple operations from Directus at once by their IDs. This action cannot be undone. Example: {ids: [

Server Directus MCP Server skeyelab/directus-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_operations does on Directus MCP Server

AI agents call delete_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.

Why delete_operations needs a policy

The tool permanently and irreversibly deletes data (operations) from the Directus instance. The explicit statement 'This action cannot be undone' confirms destructive intent. While the blast radius depends on which operations are deleted, the capability to bulk-delete without reversal places this in the Destructive category, which outranks Write.

From the tool's definition 'Delete multiple operations from Directus at once by their IDs. This action cannot be undone.'

Questions about delete_operations

What does the delete_operations tool do? +

Delete multiple operations from Directus at once by their IDs. This action cannot be undone. Example: {ids: [. 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.

How do I enforce a policy on delete_operations? +

Register the Directus MCP Server MCP server in PolicyLayer and add a rule for delete_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.

What risk level is delete_operations? +

delete_operations is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_operations? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_operations completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_operations? +

delete_operations is provided by the Directus MCP Server MCP server (skeyelab/directus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

delete_operations is one line of Directus MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.