git_remote

Run git commands on a remote server via SSH.

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/git-remote.md

WHAT IT DOES

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.

RISK

Why git_remote is rated High

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

git_remote Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_remote": {
      "limits": [
        {
          "counter": "git_remote_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 git_remote call is checked against it from then on.

FAQ

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.

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 →