Medium Risk

create_base_automation

create_base_automation

How to control create_base_automation ↓

What create_base_automation does on Odoo Dev MCP

AI agents use create_base_automation to create or update resources in Odoo Dev MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Odoo Dev MCP environment.

Medium Risk

Why create_base_automation needs a policy

The tool creates automation configurations in Odoo, which is a Write operation—it adds or modifies data that can be undone. While base automations can trigger consequential actions, the tool itself is creating configuration records, not executing those actions directly.

From the tool's definition Tool name 'create_base_automation' indicates creation of Odoo base automation rules. Sibling tools like 'create_odoo_model', 'create_odoo_module', 'create_security_rules' all perform Write operations (creation/modification).

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

How to control create_base_automation

PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Dev MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_base_automation:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_base_automation": {
      "limits": [
        {
          "counter": "create_base_automation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_base_automation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Odoo Dev 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_base_automation

What does the create_base_automation tool do? +

create_base_automation. It is categorised as a Write tool in the Odoo Dev MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_base_automation? +

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

What risk level is create_base_automation? +

create_base_automation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_base_automation? +

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

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

create_base_automation is provided by the Odoo Dev MCP server (mart337i/odoo-dev-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 Dev MCP tool call.

Start from Odoo Dev 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.

25 Odoo Dev 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.