Permanently deletes a document from Oblio via DELETE /api/docs/{type}.
AI agents call delete_document to permanently remove resources in Oblio — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (documents) from an accounting system and cannot be undone. Even though the blast radius is somewhat constrained to individual documents rather than entire databases, the financial and regulatory context (this is an accounting/invoicing system handling e-Factura in Romania) makes unintended deletion high-impact.
From the tool's definition Tool permanently deletes a document from Oblio via DELETE /api/docs/{type}. The description explicitly states 'Permanently deletes' and uses HTTP DELETE method, which is the standard REST verb for irreversible removal.
Attacks that exploit this kind of access
Permanently deletes a document from Oblio via DELETE /api/docs/{type}. It is categorised as a Destructive tool in the Oblio MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Oblio 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 Oblio. 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 Oblio MCP server (valentinludu/oblio-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 →