New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

ee_deploy

Deploy EE from buffer to target (rsync). Buffered mode only.

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

Questions about ee_deploy

What does the ee_deploy tool do? +

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.

How do I enforce a policy on ee_deploy? +

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.

What risk level is ee_deploy? +

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

Can I rate-limit ee_deploy? +

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.

How do I block ee_deploy completely? +

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.

What MCP server provides ee_deploy? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Odoo Claude's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.