manage_translations · Odoo- MCP: Risk & Policy

WHAT IT DOES

What manage_translations does on Odoo-MCP

AI agents use manage_translations 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 manage_translations needs a policy

Managing translations requires creating or modifying translation records and localization data. While not destructive (translations can be updated), this is a Write operation that creates or modifies data reversibly. Severity is high due to potential blast radius if translations are corrupted or maliciously modified across an ERP system affecting multiple languages and business operations.

From the tool's definition Tool name 'manage_translations' combined with server context showing 'managing' operations and sibling tools including create_record, copy_records, delete_records indicates data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_translations Rate-limited

manage_translations 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": {
    "manage_translations": {
      "limits": [
        {
          "counter": "manage_translations_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 manage_translations

What does the manage_translations tool do? +

Translation and localization management. 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 manage_translations? +

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

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

Can I rate-limit manage_translations? +

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

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

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