Writes data to an interactive terminal session.
AI agents invoke mcp_ssh_mcp_writeToTerminal to trigger actions in Mcp 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.
Writing to an interactive terminal session means sending commands or input to a running shell/process on a remote SSH server. This can trigger arbitrary command execution depending on what is written, making it effectively an Execute-category tool. The blast radius is high because it can run any command on a remote system.
From the tool's definition Writes data to an interactive terminal session
Documented attack patterns abuse exactly the kind of access mcp_ssh_mcp_writeToTerminal gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ssh, and nothing reaches the server without passing your rules. This is the rule we recommend for mcp_ssh_mcp_writeToTerminal:
{
"version": "1",
"default": "deny",
"tools": {
"mcp_ssh_mcp_writeToTerminal": {
"limits": [
{
"counter": "mcp_ssh_mcp_writetoterminal_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} mcp_ssh_mcp_writeToTerminal 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.
Writes data to an interactive terminal session. It is categorised as a Execute tool in the Mcp Ssh MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Ssh MCP server in PolicyLayer and add a rule for mcp_ssh_mcp_writeToTerminal: 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 Mcp Ssh. Nothing to install.
mcp_ssh_mcp_writeToTerminal 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 mcp_ssh_mcp_writeToTerminal 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 mcp_ssh_mcp_writeToTerminal. 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.
mcp_ssh_mcp_writeToTerminal is provided by the Mcp Ssh MCP server (shuakami/mcp-ssh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 Mcp Ssh tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
23 Mcp Ssh tools catalogued and risk-classified — across an index of 42,500+ MCP servers.