oca_clone_all
Clone all OCA repositories for a branch using oca-clone-everything.
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/oca-clone-all.md
What oca_clone_all does on Odoo Claude MCP
AI agents invoke oca_clone_all 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_clone_all is rated High
This tool executes an external operation (oca-clone-everything) that clones multiple repositories. It triggers a substantial external process that creates files/directories on the filesystem at scale. While cloning is not purely destructive, it executes a system-level operation with potentially large side effects (disk usage, network operations, filesystem changes), making Execute the appropriate category.
From the tool's definition Clone all OCA repositories for a branch using oca-clone-everything
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs oca_clone_all 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_clone_all, this is the rule to start with:
oca_clone_all 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_clone_all call is checked against it from then on.
Questions about oca_clone_all
Clone all OCA repositories for a branch using oca-clone-everything. 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_clone_all: 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_clone_all 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_clone_all 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_clone_all. 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_clone_all 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