High Risk →

ai_pipeline_run

Execute an Odoo-defined pipeline (ai.pipeline.step records for the

How to control ai_pipeline_run ↓

What ai_pipeline_run does on Odoo Claude MCP

AI agents invoke ai_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.

High Risk

Why ai_pipeline_run needs a policy

This tool triggers execution of Odoo pipeline steps, which are external operations defined within the Odoo instance. The actual impact depends on what those pipeline steps do (they could modify data, call APIs, process invoices, etc.), making it Execute rather than Write.

From the tool's definition Tool name "ai_pipeline_run" combined with description "Execute an Odoo-defined pipeline (ai.pipeline.step records for the" — the verb "Execute" explicitly indicates code/command execution.

Documented attack patterns abuse exactly the kind of access ai_pipeline_run gives an agent:

How to control ai_pipeline_run

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_pipeline_run:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ai_pipeline_run": {
      "limits": [
        {
          "counter": "ai_pipeline_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

ai_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.

  1. Create a free account and register Odoo Claude MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about ai_pipeline_run

What does the ai_pipeline_run tool do? +

Execute an Odoo-defined pipeline (ai.pipeline.step records for the. 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.

How do I enforce a policy on ai_pipeline_run? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for ai_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.

What risk level is ai_pipeline_run? +

ai_pipeline_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ai_pipeline_run? +

Yes. Add a rate_limit block to the ai_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.

How do I block ai_pipeline_run completely? +

Set action: deny in the PolicyLayer policy for ai_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.

What MCP server provides ai_pipeline_run? +

ai_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.

Enforce policy on every Odoo Claude MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.