High Risk →

ee_update

Git pull Enterprise repository.

How to control ee_update ↓

What ee_update does on Odoo Claude MCP

AI agents invoke ee_update to trigger actions in Odoo Claude MCP. 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.

High Risk

Why ee_update needs a policy

This tool executes a git pull operation on the Enterprise repository, which triggers external operations (network fetch + code checkout) that modify the filesystem by updating source code. It's an Execute-category action because it runs an external command whose effects depend on the current state of the repository.

From the tool's definition Git pull Enterprise repository

Documented attack patterns abuse exactly the kind of access ee_update gives an agent:

How to control ee_update

PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Claude MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for ee_update:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ee_update": {
      "limits": [
        {
          "counter": "ee_update_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Odoo Claude MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about ee_update

What does the ee_update tool do? +

Git pull Enterprise repository. It is categorised as a Execute tool in the Odoo Claude MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ee_update? +

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

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

Can I rate-limit ee_update? +

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

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

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

Enforce policy on every Odoo Claude MCP tool call.

Start from Odoo Claude MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

180 Odoo Claude MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.