Validate draft invoice
AI agents invoke validate_invoice to trigger actions in Dolibarr MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Validating an invoice is an irreversible state transition that makes the invoice official and actionable (e.g., payable, sendable to customer). This is an external operation with significant business consequences — it cannot simply be undone like a write operation.
From the tool's definition Validate draft invoice — triggers a state transition on a financial document, moving it from draft to validated/confirmed status
Attacks that exploit this kind of access
Validate draft invoice. It is categorised as a Execute tool in the Dolibarr MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Dolibarr MCP Server MCP server in PolicyLayer and add a rule for validate_invoice: 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.
validate_invoice is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the validate_invoice 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 validate_invoice. 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.
validate_invoice is provided by the Dolibarr MCP Server MCP server (marioser/dolibarr-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 →