Delete a document by ID
AI agents call delete-document to permanently remove resources in Ravendb — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible destructive operation on database records. Deletion cannot be undone without database backups or transaction rollback. The blast radius is significant as an AI agent could permanently remove critical business data, customer records, or other important documents if misused or given incorrect document IDs.
From the tool's definition Tool name 'delete-document' combined with description 'Delete a document by ID' indicates irreversible deletion of data from a RavenDB database.
Attacks that exploit this kind of access
Delete a document by ID. It is categorised as a Destructive tool in the Ravendb MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ravendb MCP server in PolicyLayer and add a rule for delete-document: 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 Ravendb. Nothing to install.
delete-document 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-document 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-document. 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-document is provided by the Ravendb MCP server (johnib/ravendb-mcp). 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 →