AI agents call odoo_get_partner_summary to retrieve information from Odooclaw without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix strongly suggests a read operation that queries or retrieves partner data. No description is provided, which lowers confidence slightly, but the naming convention and context of a CRUD tool set on Odoo ERP indicates this performs a data retrieval with no side effects. Partners in ERP systems are customer/vendor entities; retrieving a summary has minimal blast radius if misused by an agent.
From the tool's definition Tool name 'odoo_get_partner_summary' uses 'get' verb, which typically retrieves data without modification. The name indicates retrieval of partner summary information from Odoo ERP.
Attacks that exploit this kind of access
odoo_get_partner_summary. It is categorised as a Read tool in the Odooclaw MCP Server, which means it retrieves data without modifying state.
Register the Odooclaw MCP server in PolicyLayer and add a rule for odoo_get_partner_summary: 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 Odooclaw. Nothing to install.
odoo_get_partner_summary 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_get_partner_summary 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_get_partner_summary. 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_get_partner_summary is provided by the Odooclaw MCP server (nicolasramos/odooclaw-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 →