BEST tool for customer proposals. Get proposals for a specific customer with flexible status filtering. Use statuses=[0,1] for open/pending, status=2 for won, status=3 for lost. If no status filter specified, returns ALL proposals. First use search_customers to get the socid if you only have the ...
AI agents call get_customer_proposals to retrieve information from Dolibarr MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries proposal data from Dolibarr with filtering options (by status). It has no side effects—it does not create, modify, delete, or execute any operations. The filtering parameters (status values) only control what data is returned, not what happens to the data. This is a standard Read operation with minimal risk.
From the tool's definition Tool description explicitly states 'Get proposals for a specific customer' with filtering capabilities. The verb 'Get' and the passive retrieval of existing proposal data with no mention of modification, deletion, or execution indicates a read-only operation.
Attacks that exploit this kind of access
BEST tool for customer proposals. Get proposals for a specific customer with flexible status filtering. Use statuses=[0,1] for open/pending, status=2 for won, status=3 for lost. If no status filter specified, returns ALL proposals. First use search_customers to get the socid if you only have the customer name. It is categorised as a Read tool in the Dolibarr MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dolibarr MCP Server MCP server in PolicyLayer and add a rule for get_customer_proposals: 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.
get_customer_proposals is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_customer_proposals 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 get_customer_proposals. 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.
get_customer_proposals 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 →