Delete data from Dolibarr API using DELETE method
AI agents call dolibarr_delete to permanently remove resources in Dolibarr MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool directly deletes data from a business-critical ERP/CRM system (Dolibarr). Deletions are irreversible and cannot be undone. In the context of an AI agent, misuse could result in permanent loss of customer records, product information, orders, or other critical business data. This meets the Destructive category definition.
From the tool's definition Tool name is 'dolibarr_delete' and description states 'Delete data from Dolibarr API using DELETE method'. Explicitly performs irreversible deletion operations on ERP/CRM data.
Attacks that exploit this kind of access
Delete data from Dolibarr API using DELETE method. It is categorised as a Destructive tool in the Dolibarr MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dolibarr MCP Server MCP server in PolicyLayer and add a rule for dolibarr_delete: 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 Dolibarr MCP Server. Nothing to install.
dolibarr_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 dolibarr_delete 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 dolibarr_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.
dolibarr_delete is provided by the Dolibarr MCP Server MCP server (ivanmartin33/dolibarr-mcp-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 →