Execute a command on the connected Linux host. IMPORTANT: Destructive commands (rm -rf, dd, shutdown, etc.) ALWAYS require explicit confirmation before execution. Supports sudo commands.
AI agents invoke ssh_execute to trigger actions in SSH Linux Control. 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.
This tool runs arbitrary shell commands on a remote Linux system, triggering external operations (system calls) whose effects depend entirely on the arguments provided. While the server implements a safety check requiring confirmation for known destructive patterns, the tool itself remains Execute-class because: (1) it can trigger irreversible system changes when confirmation is given, (2) it has no reversibility…
From the tool's definition Tool explicitly described as 'Execute a command on the connected Linux host' with support for 'sudo commands'.
Attacks that exploit this kind of access
Execute a command on the connected Linux host. IMPORTANT: Destructive commands (rm -rf, dd, shutdown, etc.) ALWAYS require explicit confirmation before execution. Supports sudo commands. It is categorised as a Execute tool in the SSH Linux Control MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SSH Linux Control 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 SSH Linux Control. Nothing to install.
ssh_execute 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_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.
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.
ssh_execute is provided by the SSH Linux Control MCP server (yutooop/mcp_linux_administration_ssh-openwebui_tool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →