Delete a JSON document by ID from a document database
AI agents call delete_json_doc_from_db to permanently remove resources in MCP JSON Document Collection Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes documents from a database with no undo capability. While the blast radius is limited to a single document at a time (compared to delete_json_doc_database which deletes entire databases), document deletion is still irreversible data loss.
From the tool's definition Tool name 'delete_json_doc_from_db' and description 'Delete a JSON document by ID from a document database' explicitly perform irreversible deletion of data.
Attacks that exploit this kind of access
Delete a JSON document by ID from a document database. It is categorised as a Destructive tool in the MCP JSON Document Collection Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP JSON Document Collection Server MCP server in PolicyLayer and add a rule for delete_json_doc_from_db: 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 MCP JSON Document Collection Server. Nothing to install.
delete_json_doc_from_db 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_json_doc_from_db 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_json_doc_from_db. 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_json_doc_from_db is provided by the MCP JSON Document Collection Server MCP server (jimpick/mcp-json-db-collection-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 →