ssh_execute · MCP Remote Access MCP: Risk & Policy

WHAT IT DOES

What ssh_execute does on MCP Remote Access

AI agents invoke ssh_execute to trigger actions in MCP Remote Access. 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.

WHY IT NEEDS A POLICY

Why ssh_execute needs a policy

This tool allows execution of arbitrary commands on remote devices (Raspberry Pi, embedded systems, IoT devices) with full access to stdout, stderr, and exit codes. The blast radius is critical because: (1) an AI agent could execute destructive commands (rm -rf, killall), financial transactions, or malicious code; (2) it operates on network-exposed remote systems without inherent safeguards on command content; (3)…

From the tool's definition Tool description states: 'Execute a command on a connected SSH host. Returns stdout, stderr, and exit code.' The capability to run arbitrary commands on remote systems via SSH is a classic Execute operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Remote Access, so you can run agents against it safely.

FAQ

Questions about ssh_execute

What does the ssh_execute tool do? +

Execute a command on a connected SSH host. Returns stdout, stderr, and exit code. It is categorised as a Execute tool in the MCP Remote Access 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 MCP Remote Access 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 MCP Remote Access. 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 MCP Remote Access MCP server (rfingadam/mcp-remote-access). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.