Update existing data in Dolibarr API using PUT method
AI agents use dolibarr_put to create or update resources in Dolibarr MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dolibarr MCP Server environment.
This tool modifies data reversibly through updates rather than creating new resources (Write rather than Execute). While it operates on business-critical ERP/CRM data (orders, products, customer records), the operation itself is not destructive (no deletion/purge), not financial (no money movement), and not code execution.
From the tool's definition Tool description states 'Update existing data in Dolibarr API using PUT method'. The PUT HTTP method is used to modify existing resources.
Attacks that exploit this kind of access
Update existing data in Dolibarr API using PUT method. It is categorised as a Write tool in the Dolibarr MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dolibarr MCP Server MCP server in PolicyLayer and add a rule for dolibarr_put: 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_put is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dolibarr_put 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_put. 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_put 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 →