execute_approved_write · Odoo MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_approved_write does on Odoo MCP Server

AI agents use execute_approved_write 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.

WHY IT NEEDS A POLICY

Why execute_approved_write needs a policy

This tool executes a write operation on an Odoo ERP system. While it implies a prior approval/preview step (suggesting some guardrails), it still modifies data in an ERP system. The severity is high because ERP data modifications can affect business-critical records (inventory, customers, orders, etc.) across the system, and misuse could corrupt important business data.

From the tool's definition Execute a previously previewed and confirmed standard write

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_approved_write Rate-limited

execute_approved_write 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": {
    "execute_approved_write": {
      "limits": [
        {
          "counter": "execute_approved_write_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 Server, so you can run agents against it safely.

FAQ

Questions about execute_approved_write

What does the execute_approved_write tool do? +

Execute a previously previewed and confirmed standard write. 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 execute_approved_write? +

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

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

Can I rate-limit execute_approved_write? +

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

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

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