Dashboard aggregation: counts of vendor bill moves by next_step
AI agents call ai_invoice_pipeline_summary to retrieve information from Odoo Claude MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads/aggregates existing invoice pipeline data to display summary counts. It has no side effects, does not create or modify records, and does not execute arbitrary operations. The blast radius of misuse is minimal—an agent could at worst retrieve summary statistics that are already accessible within the Odoo instance. This is a classic Read operation.
From the tool's definition Tool performs 'dashboard aggregation' and 'counts' — it retrieves and summarizes data about vendor bill moves without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access ai_invoice_pipeline_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Claude MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for ai_invoice_pipeline_summary:
{
"version": "1",
"default": "deny",
"tools": {
"ai_invoice_pipeline_summary": {}
}
} ai_invoice_pipeline_summary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Dashboard aggregation: counts of vendor bill moves by next_step. It is categorised as a Read tool in the Odoo Claude MCP MCP Server, which means it retrieves data without modifying state.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for ai_invoice_pipeline_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 Odoo Claude MCP. Nothing to install.
ai_invoice_pipeline_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 ai_invoice_pipeline_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 ai_invoice_pipeline_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.
ai_invoice_pipeline_summary is provided by the Odoo Claude MCP server (rosenvladimirov/odoo-claude-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Odoo Claude MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
180 Odoo Claude MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.