List Odoo CRM leads & opportunities (crm.lead). Returns name, contact, email_from, expected_revenue, probability, stage_id, and type (lead/opportunity). Use for "open opportunities" or "sales pipeline".
Risk signalsAccepts URL/endpoint input (url)
Part of the Odoo server.
Free to start. No card required.
AI agents call odoo_list_crm_leads to retrieve information from Odoo without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though odoo_list_crm_leads only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"odoo_list_crm_leads": {}
}
}See the full Odoo policy for all 25 tools.
These attack patterns abuse exactly the kind of access odoo_list_crm_leads gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
List Odoo CRM leads & opportunities (crm.lead). Returns name, contact, email_from, expected_revenue, probability, stage_id, and type (lead/opportunity). Use for "open opportunities" or "sales pipeline".. It is categorised as a Read tool in the Odoo MCP Server, which means it retrieves data without modifying state.
Register the Odoo MCP server in PolicyLayer and add a rule for odoo_list_crm_leads: 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 Odoo. Nothing to install.
odoo_list_crm_leads 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 odoo_list_crm_leads 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 odoo_list_crm_leads. 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.
odoo_list_crm_leads is provided by the Odoo MCP server (https://gateway.pipeworx.io/odoo/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Odoo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.