High Risk →

ssh_exec_raw

Execute command over SSH with array arguments that are safely quoted for the remote shell

How to control ssh_exec_raw ↓

What ssh_exec_raw does on SSH MCP Server

AI agents invoke ssh_exec_raw to trigger actions in SSH MCP Server. 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 ssh_exec_raw needs a policy

This tool executes commands on remote systems via SSH. Execution tools present high severity risk because their effects depend entirely on the arguments provided—an AI agent could run destructive, malicious, or unintended commands (rm, data exfiltration, lateral movement, etc.).

From the tool's definition Tool name 'ssh_exec_raw' and description 'Execute command over SSH' directly indicate command execution. The phrase 'safely quoted for the remote shell' confirms this tool runs arbitrary commands on remote systems.

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

How to control ssh_exec_raw

PolicyLayer is an MCP gateway — it sits between your AI agents and SSH MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ssh_exec_raw:

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

ssh_exec_raw 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 SSH MCP Server — 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 ssh_exec_raw

What does the ssh_exec_raw tool do? +

Execute command over SSH with array arguments that are safely quoted for the remote shell. It is categorised as a Execute tool in the SSH MCP Server 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_exec_raw? +

Register the SSH MCP Server MCP server in PolicyLayer and add a rule for ssh_exec_raw: 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 SSH MCP Server. Nothing to install.

What risk level is ssh_exec_raw? +

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

Can I rate-limit ssh_exec_raw? +

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

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

ssh_exec_raw is provided by the SSH MCP Server MCP server (kinothe-kafkaesque/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SSH MCP Server tool call.

Start from SSH MCP Server, 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.

15 SSH MCP Server 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.