Destructive operations that remove data. Supported operations: delete_element, clear, clear_github_auth Element types: persona, skill, template, agent, memory, ensemble These operations remove data. Use with caution. ⚠️ SECURITY: Do not auto-allow this endpoint in your host settings (e.g., Cl...
Part of the DollhouseMCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents may call mcp_aql_delete to permanently remove or destroy resources in DollhouseMCP. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call mcp_aql_delete in a loop, permanently destroying resources in DollhouseMCP. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
tools:
mcp_aql_delete:
rules:
- action: deny
reason: "Blocked by default — enable with approval"See the full DollhouseMCP policy for all 5 tools.
Agents calling destructive-class tools like mcp_aql_delete have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
mcp_aql_delete is one of the critical-risk operations in DollhouseMCP. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.
Destructive operations that remove data. Supported operations: delete_element, clear, clear_github_auth Element types: persona, skill, template, agent, memory, ensemble These operations remove data. Use with caution. ⚠️ SECURITY: Do not auto-allow this endpoint in your host settings (e.g., Claude Code settings.json). Each delete operation should require explicit human approval. Auto-allowing bypasses the per-operation confirmation gate, leaving only element deny policies as protection against unintended data loss. Quick start examples: { operation: "delete_element", element_type: "persona", params: { element_name: "Old-Persona" } } { operation: "clear", params: { element_name: "temp-notes" } } { operation: "clear_github_auth" } Discover required parameters — use mcp_aql_read: { operation: "introspect", params: { query: "operations", name: "delete_element" } }. It is categorised as a Destructive tool in the DollhouseMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for mcp_aql_delete. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the DollhouseMCP MCP server.
mcp_aql_delete 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 mcp_aql_delete rule in your Intercept 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 Intercept policy for mcp_aql_delete. 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.
mcp_aql_delete is provided by the DollhouseMCP MCP server (@dollhousemcp/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept