oca_deploy
Deploy OCA repos from buffer to target (rsync). Only in buffered mode.
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/oca-deploy.md
What oca_deploy does on Odoo Claude MCP
AI agents invoke oca_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 oca_deploy is rated High
This tool executes a deployment operation (rsync) that modifies filesystem state on a target system. While not immediately destructive (rsync by default doesn't delete), it irreversibly propagates code/configuration changes to target infrastructure. An AI agent could misuse this to push malicious code to production systems, corrupt deployments, or create denial-of-service conditions.
From the tool's definition Tool description states 'Deploy OCA repos from buffer to target (rsync)' — rsync is a file synchronization command that executes on remote systems to copy/update files.
Attacks that exploit this kind of access
The rule that runs oca_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 oca_deploy, this is the rule to start with:
oca_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 oca_deploy call is checked against it from then on.
Questions about oca_deploy
Deploy OCA repos from buffer to target (rsync). Only in buffered mode. 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 oca_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.
oca_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 oca_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 oca_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.
oca_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