execute-command · Ssh MCP: Risk & Policy

WHAT IT DOES

What execute-command does on Ssh

AI agents invoke execute-command to trigger actions in Ssh. 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 execute-command needs a policy

This tool allows execution of arbitrary shell commands on remote systems, with outcomes entirely dependent on what command an AI agent chooses to run. While the server claims to apply 'command-level security controls', the tool itself presents a critical risk because a misdirected agent or prompt injection could result in unauthorized data exfiltration, system compromise, lateral movement, or destruction.

From the tool's definition Tool is named 'execute-command' and described as 'Execute command on connected server and get output result'. This directly executes arbitrary commands on remote servers.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute-command Rate-limited

execute-command 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": {
    "execute-command": {
      "limits": [
        {
          "counter": "execute-command_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 Ssh, so you can run agents against it safely.

FAQ

Questions about execute-command

What does the execute-command tool do? +

Execute command on connected server and get output result. It is categorised as a Execute tool in the Ssh MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute-command? +

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

What risk level is execute-command? +

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

Can I rate-limit execute-command? +

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

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

execute-command is provided by the Ssh MCP server (xiyueyy/ssh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.