execute_scheduled_action · Odoo- MCP: Risk & Policy

WHAT IT DOES

What execute_scheduled_action does on Odoo-MCP

AI agents invoke execute_scheduled_action to trigger actions in Odoo-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 IT NEEDS A POLICY

Why execute_scheduled_action needs a policy

This tool directly executes automated business processes and scheduled tasks within Odoo. While not destructive by itself, scheduled actions can perform writes, deletes, or external API calls depending on their configuration. The blast radius is high because a malicious agent could trigger unintended automated workflows, mass data modifications, or external integrations.

From the tool's definition Tool description states 'Execute scheduled actions and cron jobs' — the verb 'Execute' indicates running external operations and triggers.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_scheduled_action Rate-limited

execute_scheduled_action 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": {
    "execute_scheduled_action": {
      "limits": [
        {
          "counter": "execute_scheduled_action_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Odoo-MCP, so you can run agents against it safely.

FAQ

Questions about execute_scheduled_action

What does the execute_scheduled_action tool do? +

Execute scheduled actions and cron jobs. It is categorised as a Execute tool in the Odoo-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 execute_scheduled_action? +

Register the Odoo- MCP server in PolicyLayer and add a rule for execute_scheduled_action: 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-MCP. Nothing to install.

What risk level is execute_scheduled_action? +

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

Can I rate-limit execute_scheduled_action? +

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

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

execute_scheduled_action is provided by the Odoo- MCP server (ridrisa/odoo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.