ai_pipeline_run

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

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/ai-pipeline-run.md

WHAT IT DOES

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.

RISK

Why ai_pipeline_run is rated High

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ai_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_pipeline_run, this is the rule to start with:

ai_pipeline_run Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every ai_pipeline_run call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

More on Odoo Claude, and thousands of servers like it.

This server

All 246 Odoo Claude tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →