ee_update

Git pull Enterprise repository.

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp

High RISK CLASS

Category Execute

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/ee-update.md

WHAT IT DOES

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.

RISK

Why ee_update is rated High

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ee_update 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 ee_update, this is the rule to start with:

ee_update Rate-limited

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.

View as policy code

policy.json

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

RATE-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 ee_update call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

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

This server

All 246 Odoo Claude tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →