ssh_execute

Execute a command 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/ssh-execute.md

WHAT IT DOES

What ssh_execute does on Odoo Claude MCP

AI agents invoke ssh_execute 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 ssh_execute is rated High

This tool allows running arbitrary shell commands on remote servers, giving an AI agent the ability to trigger external operations with unpredictable effects depending on the command argument. The blast radius is critical—an agent could modify files, exfiltrate data, pivot to other systems, or cause widespread damage.

From the tool's definition Tool name 'ssh_execute' combined with description 'Execute a command on a remote server via SSH' explicitly indicates execution of arbitrary commands on remote systems.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ssh_execute Rate-limited

ssh_execute 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": {
    "ssh_execute": {
      "limits": [
        {
          "counter": "ssh_execute_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 ssh_execute call is checked against it from then on.

FAQ

Questions about ssh_execute

What does the ssh_execute tool do? +

Execute a command 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 ssh_execute? +

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

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

Can I rate-limit ssh_execute? +

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

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

ssh_execute 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

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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