Delete a dashboard from Directus by ID. This action cannot be undone.
AI agents call delete_dashboard 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.
The tool permanently removes a dashboard without recovery option. While the blast radius is scoped to a single dashboard rather than bulk data deletion, the irreversible nature and explicit warning that the action 'cannot be undone' places this squarely in the Destructive category rather than Write. An AI agent misusing this could permanently destroy dashboards configured by users, with no undo capability.
From the tool's definition 'Delete a dashboard from Directus by ID. This action cannot be undone.' - explicitly states the action is irreversible and cannot be undone, meeting the definition of destructive operations.
Attacks that exploit this kind of access
Delete a dashboard from Directus by ID. This action cannot be undone. 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 delete_dashboard: 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.
delete_dashboard 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_dashboard 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_dashboard. 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_dashboard 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.
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 →