oca_clone_repo

Clone a specific OCA repository by name.

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/oca-clone-repo.md

WHAT IT DOES

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.

RISK

Why oca_clone_repo is rated High

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs oca_clone_repo 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_repo, this is the rule to start with:

oca_clone_repo Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every oca_clone_repo call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

More on Odoo Claude, and thousands of servers like it.

This server

All 246 Odoo Claude tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →