migrate_history

ADMIN: list past migration assessments. Read-only.

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/migrate-history.md

WHAT IT DOES

What migrate_history does on Odoo Claude MCP

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

RISK

Why migrate_history is rated Medium

An AI agent can call migrate_history faster than any human can review: one bad instruction and it creates or modifies resources in Odoo Claude MCP by the hundred, each call as confident as the last.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs migrate_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Odoo Claude MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For migrate_history, this is the rule to start with:

migrate_history Rate-limited

migrate_history 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": {
    "migrate_history": {
      "limits": [
        {
          "counter": "migrate_history_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every migrate_history call is checked against it from then on.

FAQ

Questions about migrate_history

What does the migrate_history tool do? +

ADMIN: list past migration assessments. Read-only. It is categorised as a Write tool in the Odoo Claude 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 migrate_history? +

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

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

Can I rate-limit migrate_history? +

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

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

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

KEEP EXPLORING

More on Odoo Claude, and thousands of servers like it.

This server

All 246 Odoo Claude tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →