AI agents call odoo_get_invoice_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.
This tool retrieves invoice information (account.move records) and their line items. The verb 'get' and the retrieval-focused description indicate a read-only query operation with no data modification, deletion, execution of code, or financial transactions. The blast radius of misuse is minimal—an agent could retrieve sensitive financial information, but cannot alter or delete records or move money.
From the tool's definition Tool name contains 'get' and description states 'Get complete details of a specific invoice', which retrieves data without modification or side effects.
Attacks that exploit this kind of access
Get complete details of a specific invoice (account.move), including lines. 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_invoice_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_invoice_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_invoice_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_invoice_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_invoice_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 →