existdb_delete_resource

THE RISK

Critical Risk

Why existdb_delete_resource needs a policy

This tool permanently deletes data with no undo capability, meeting the definition of Destructive category. It operates on eXist-db resources (documents or collections), which may contain valuable digital humanities data (TEI/XML). The severity is high rather than critical because the blast radius depends on the specific resource targeted, but any unintended deletion would cause permanent data loss.

From the tool's definition Tool name is 'existdb_delete_resource' and description explicitly states 'Deletes a document or collection from eXist-db' and 'deletion is permanent.' The word 'permanent' confirms irreversible data loss.

Documented attack patterns abuse exactly the kind of access existdb_delete_resource gives an agent:

POLICY

How to control existdb_delete_resource

PolicyLayer is an MCP gateway — it sits between your AI agents and Existdb, and nothing reaches the server without passing your rules. This is the rule we recommend for existdb_delete_resource:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "existdb_delete_resource"
  ]
}

existdb_delete_resource disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Existdb — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Existdb tools

Execute existdb_execute_query Executes an XQuery expression against a live eXist-db instance via the REST API Write existdb_store_document Stores (creates or replaces) an XML document in an eXist-db collection via PUT. Write existdb_create_collection Creates a new sub-collection inside an existing eXist-db collection. Read existdb_get_document Retrieves the XML content of a document stored in eXist-db. Read existdb_get_xquery_snippet Returns a ready-to-use XQuery code snippet for a common eXist-db programming pattern. Read existdb_list_collection Lists the contents of an eXist-db collection: sub-collections and XML documents Read existdb_list_namespace_functions Lists all documented functions in a given eXist-db / XQuery namespace. Read existdb_list_namespaces Returns a summary table of all available namespaces in the documentation cache,

All 12 Existdb tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Existdb → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about existdb_delete_resource

What does the existdb_delete_resource tool do? +

Deletes a document or collection from eXist-db. Use with caution — deletion is permanent. It is categorised as a Destructive tool in the Existdb 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 existdb_delete_resource? +

Register the Existdb MCP server in PolicyLayer and add a rule for existdb_delete_resource: 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 Existdb. Nothing to install.

What risk level is existdb_delete_resource? +

existdb_delete_resource 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 existdb_delete_resource? +

Yes. Add a rate_limit block to the existdb_delete_resource 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 existdb_delete_resource completely? +

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

existdb_delete_resource is provided by the Existdb MCP server (orazionelson/existdb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Existdb tool call.

Start from Existdb, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →