Execute a command on an SSH target. If the response has status
AI agents invoke ssh_exec to trigger actions in Shellgate. 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.
SSH command execution is inherently an Execute risk—it triggers external operations (shell commands on remote servers) whose effects depend on the arguments provided. While the server description mentions 'scoped tokens' and 'human-in-the-loop for dangerous commands' as mitigations, the tool itself is fundamentally capable of running arbitrary code on remote systems, making it Execute rather than Read or Write.
From the tool's definition Tool name is 'ssh_exec' and description states 'Execute a command on an SSH target.' This directly executes arbitrary commands on remote systems via SSH.
Documented attack patterns abuse exactly the kind of access ssh_exec gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Shellgate, and nothing reaches the server without passing your rules. This is the rule we recommend for ssh_exec:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_exec": {
"limits": [
{
"counter": "ssh_exec_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Execute a command on an SSH target. If the response has status. It is categorised as a Execute tool in the Shellgate MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Shellgate 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 Shellgate. Nothing to install.
ssh_exec is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
ssh_exec is provided by the Shellgate MCP server (matthiastjong/shellgate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Shellgate, 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.
31 Shellgate tools catalogued and risk-classified — across an index of 43,000+ MCP servers.