ee_deploy
Deploy EE from buffer to target (rsync). Buffered mode only.
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/ee-deploy.md
What ee_deploy does on Odoo Claude MCP
AI agents invoke ee_deploy 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.
Why ee_deploy is rated High
This tool triggers external operations (rsync deployment) whose effects depend on arguments (source buffer, target location, file filters). It can modify system files and application code, affecting the running Odoo instance. While not immediately destructive (rsync is reversible in principle), the scope and blast radius of deploying potentially untested code to a live system makes this Execute-level risk.
From the tool's definition The tool performs 'Deploy EE from buffer to target (rsync)' — this is an active deployment operation that executes rsync commands to transfer and potentially install code/binaries to a target system.
Attacks that exploit this kind of access
The rule that runs ee_deploy 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_deploy, this is the rule to start with:
ee_deploy 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every ee_deploy call is checked against it from then on.
Questions about ee_deploy
Deploy EE from buffer to target (rsync). Buffered mode only. 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.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for ee_deploy: 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.
ee_deploy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ee_deploy 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.
Set action: deny in the PolicyLayer policy for ee_deploy. 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.
ee_deploy 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.
More on Odoo Claude, and thousands of servers like it.
Across the catalogue