ssh_exec

SSH remote execution. Auto-selects client.

SERVERClaude C2 SOURCE0xyg3n/claude-c2

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/0xyg3n-claude-c2/ssh-exec.md

WHAT IT DOES

What ssh_exec does on Claude C2

AI agents invoke ssh_exec to trigger actions in Claude C2. 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_exec is rated High

This tool performs remote command execution over SSH, which allows an AI agent to run arbitrary commands on remote systems. Combined with the server's explicit purpose of 'command and control of remote systems' and sibling tools like amsi_bypass, bypassuac, and browser_creds that strongly suggest offensive/malicious use, this tool represents a critical risk.

From the tool's definition 'SSH remote execution. Auto-selects client.' — executes arbitrary commands on remote systems via SSH

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ssh_exec safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude C2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ssh_exec, this is the rule to start with:

ssh_exec Rate-limited

ssh_exec 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_exec": {
      "limits": [
        {
          "counter": "ssh_exec_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 Claude C2, apply this rule, and every ssh_exec call is checked against it from then on.

FAQ

Questions about ssh_exec

What does the ssh_exec tool do? +

SSH remote execution. Auto-selects client. It is categorised as a Execute tool in the Claude C2 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? +

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

What risk level is ssh_exec? +

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

Can I rate-limit ssh_exec? +

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

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

ssh_exec is provided by the Claude C2 MCP server (0xyg3n/claude-c2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude C2, and thousands of servers like it.

This server

All 94 Claude C2 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 →