import_records · Odoo- MCP: Risk & Policy

WHAT IT DOES

What import_records does on Odoo-MCP

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

WHY IT NEEDS A POLICY

Why import_records needs a policy

The tool creates or inserts multiple records into an ERP system, which is a Write operation. It does not delete (Destructive), execute code (Execute), or handle money (Financial). However, severity is high rather than medium because bulk imports in ERP systems can corrupt data integrity if misused, affect numerous dependent records, and are difficult to reverse at scale.

From the tool's definition Tool name 'import_records' combined with description 'Import records from data' indicates creation or bulk insertion of data into Odoo models.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_records Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_records": {
      "limits": [
        {
          "counter": "import_records_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 import_records

What does the import_records tool do? +

Import records from data. It is categorised as a Write tool in the Odoo-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 import_records? +

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

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

Can I rate-limit import_records? +

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

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

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