Close proposal: status 2=signed/won, 3=refused/lost
AI agents use close_proposal 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 proposal data by updating its status field, which is a write operation. While it changes an important business state, it is reversible (proposals can be reopened or status corrected), so it falls under Write rather than Destructive.
From the tool's definition Tool description states 'Close proposal: status 2=signed/won, 3=refused/lost' — this modifies the status field of a proposal record, changing it from an open state to a terminal state (signed/won or refused/lost).
Attacks that exploit this kind of access
Close proposal: status 2=signed/won, 3=refused/lost. 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 close_proposal: 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.
close_proposal 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 close_proposal 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 close_proposal. 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.
close_proposal 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 →