ai_invoice_pipeline_run
Execute the full registered step pipeline for one move+attachment.
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/ai-invoice-pipeline-run.md
What ai_invoice_pipeline_run does on Odoo Claude MCP
AI agents invoke ai_invoice_pipeline_run to trigger actions in Odoo Claude MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why ai_invoice_pipeline_run is rated High
This tool executes an automated pipeline against invoice data and attachments. While it does not directly move money (thus not Financial), it triggers potentially multi-step operations on financial documents (invoices) that could modify state, trigger downstream processes, or integrate with payment systems.
From the tool's definition Tool name contains 'run' and description explicitly states 'Execute the full registered step pipeline' — indicates execution of a predefined workflow with side effects on financial documents (invoices).
Attacks that exploit this kind of access
The rule that runs ai_invoice_pipeline_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Odoo Claude MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ai_invoice_pipeline_run, this is the rule to start with:
ai_invoice_pipeline_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every ai_invoice_pipeline_run call is checked against it from then on.
Questions about ai_invoice_pipeline_run
Execute the full registered step pipeline for one move+attachment. It is categorised as a Execute tool in the Odoo Claude MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for ai_invoice_pipeline_run: 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_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ai_invoice_pipeline_run 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_run. 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_run 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.
More on Odoo Claude, and thousands of servers like it.
Across the catalogue