Delete multiple dashboards from Directus at once by their IDs. This action cannot be undone. Example: {ids: [
AI agents call delete_dashboards 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.
This tool permanently removes dashboards and cannot be reversed, meeting the definition of Destructive. The blast radius is high because an AI agent could delete critical business dashboards in production environments, losing configuration and visibility. It is not Financial (no money involved), though it could have business impact through lost analytics access.
From the tool's definition The tool description explicitly states 'Delete multiple dashboards from Directus at once' and 'This action cannot be undone', establishing it as an irreversible deletion operation.
Attacks that exploit this kind of access
Delete multiple dashboards 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.
Register the Directus MCP Server MCP server in PolicyLayer and add a rule for delete_dashboards: 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_dashboards 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_dashboards 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_dashboards. 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_dashboards 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 →