Medium Risk

create_record

Create new records in Odoo

How to control create_record ↓

What create_record does on Odoo MCP Server

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

Medium Risk

Why create_record needs a policy

This tool creates new records in Odoo, which is a reversible write operation. It modifies the database by adding new entries but does not delete or destroy data. While creating records can have business impact (e.g., creating financial documents, orders, or customers), the operation itself is reversible through deletion or modification.

From the tool's definition Tool name 'create_record' and description 'Create new records in Odoo' indicate the tool creates new data entries in the ERP system.

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

How to control create_record

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

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

create_record 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 MCP Server — 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_record

What does the create_record tool do? +

Create new records in Odoo. It is categorised as a Write tool in the Odoo MCP Server 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_record? +

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

What risk level is create_record? +

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

Can I rate-limit create_record? +

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

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

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

Enforce policy on every Odoo MCP Server tool call.

Start from Odoo MCP Server, 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.

12 Odoo MCP Server 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.