ai_pipeline_step_execute

THE RISK

High Risk

Why ai_pipeline_step_execute needs a policy

This tool runs code/operations on a remote system (Odoo) whose effects depend on which pipeline step is specified as an argument. Pipeline steps typically perform business logic (invoice processing, document handling, etc.) that can modify data, trigger workflows, or call external services. The caller controls which step executes, making misuse high-severity.

From the tool's definition Tool name contains 'execute' and description states 'Execute a single ai.pipeline.step by name via Odoo RPC' — explicitly triggers execution of a named pipeline step in a remote Odoo instance.

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

POLICY

How to control ai_pipeline_step_execute

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

policy.json

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

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

Create a free account and register Odoo Claude MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Odoo Claude MCP tools

Destructive cf_dns_delete Delete a DNS record. Destructive cf_tunnel_route_remove Remove ingress rule by hostname + delete its CNAME record. Destructive ee_unlink Remove symlinks for EE modules from addons path. Destructive google_calendar_delete_event Delete a calendar event. Destructive memory_delete Delete a memory file from personal or shared storage. Destructive odoo_fp_remove_action Remove a tax action map entry from a fiscal position (l10n_bg_tax_admin). Destructive odoo_stock_initial_delete Delete wrong opening stock balances — cascade-removes stock.move (is_inventory=TRUE) Destructive odoo_stock_mo_delete_draft Safely DELETE a draft or cancelled mrp.production with cascade (raw stock.moves,

All 180 Odoo Claude MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Odoo Claude MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about ai_pipeline_step_execute

What does the ai_pipeline_step_execute tool do? +

Execute a single ai.pipeline.step by name via Odoo RPC. 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_step_execute? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for ai_pipeline_step_execute: 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_step_execute? +

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

Can I rate-limit ai_pipeline_step_execute? +

Yes. Add a rate_limit block to the ai_pipeline_step_execute 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_step_execute completely? +

Set action: deny in the PolicyLayer policy for ai_pipeline_step_execute. 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_step_execute? +

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

CHECK YOUR STACK →