odoo_install_module · MCP Odoo Server MCP: Risk & Policy

WHAT IT DOES

What odoo_install_module does on MCP Odoo Server

AI agents invoke odoo_install_module to trigger actions in MCP Odoo Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why odoo_install_module needs a policy

Installing a module triggers execution of module code, database schema changes, and system configuration updates in Odoo. This is an external operation with significant side effects (schema migrations, new records, activated features) that go beyond simple data writes. It cannot always be cleanly reversed and may affect system stability, making it high severity.

From the tool's definition Install an Odoo module by its technical name

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

odoo_install_module Rate-limited

odoo_install_module stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "odoo_install_module": {
      "limits": [
        {
          "counter": "odoo_install_module_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Odoo Server, so you can run agents against it safely.

FAQ

Questions about odoo_install_module

What does the odoo_install_module tool do? +

Install an Odoo module by its technical name. It is categorised as a Execute tool in the MCP Odoo Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on odoo_install_module? +

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

What risk level is odoo_install_module? +

odoo_install_module is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit odoo_install_module? +

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

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

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