High Risk →

git_remote

Run git commands on a remote server via SSH.

How to control git_remote ↓

What git_remote does on Odoo Claude MCP

AI agents invoke git_remote 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 git_remote needs a policy

This tool allows execution of arbitrary git commands on remote servers through SSH, which constitutes arbitrary command execution with network access. While nominally scoped to git, git commands can be leveraged for arbitrary code execution (e.g., git hooks, cloning malicious repos, or combined with shell metacharacters).

From the tool's definition Tool explicitly states it will "Run git commands on a remote server via SSH." Running arbitrary git commands via SSH is code execution on a remote system.

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

How to control git_remote

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 git_remote:

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

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

What does the git_remote tool do? +

Run git commands on a remote server via SSH. 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 git_remote? +

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

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

Can I rate-limit git_remote? +

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

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

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