High Risk →

oca_clone_repo

Clone a specific OCA repository by name.

How to control oca_clone_repo ↓

What oca_clone_repo does on Odoo Claude MCP

AI agents invoke oca_clone_repo 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.

High Risk

Why oca_clone_repo needs a policy

Cloning a repository involves executing a git clone operation on the server filesystem, which triggers an external operation (network fetch + disk write). This goes beyond a simple write as it executes a VCS operation that pulls external code onto the server, potentially introducing untrusted code into the environment.

From the tool's definition Clone a specific OCA repository by name

Documented attack patterns abuse exactly the kind of access oca_clone_repo gives an agent:

How to control oca_clone_repo

PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Claude MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for oca_clone_repo:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "oca_clone_repo": {
      "limits": [
        {
          "counter": "oca_clone_repo_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Odoo Claude MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about oca_clone_repo

What does the oca_clone_repo tool do? +

Clone a specific OCA repository by name. 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 oca_clone_repo? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for oca_clone_repo: 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 oca_clone_repo? +

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

Can I rate-limit oca_clone_repo? +

Yes. Add a rate_limit block to the oca_clone_repo 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 oca_clone_repo completely? +

Set action: deny in the PolicyLayer policy for oca_clone_repo. 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 oca_clone_repo? +

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

Enforce policy on every Odoo Claude MCP tool call.

Start from Odoo Claude MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

180 Odoo Claude MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.