Get recent output lines from running or completed task.
AI agents call ssh_get_task_output to retrieve information from MCP SSH Orchestrator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves output from previously executed tasks. It performs a read-only operation that queries task state without side effects. While the underlying tasks may have been Execute or Destructive operations, this tool itself merely returns their output logs. The severity is low because reading task output poses minimal risk—it does not execute commands, modify infrastructure, or delete data.
From the tool's definition Tool name 'ssh_get_task_output' and description 'Get recent output lines from running or completed task' indicate retrieval of existing task output with no modification, creation, or deletion of data.
Documented attack patterns abuse exactly the kind of access ssh_get_task_output gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP SSH Orchestrator, and nothing reaches the server without passing your rules. This is the rule we recommend for ssh_get_task_output:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_get_task_output": {}
}
} ssh_get_task_output is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get recent output lines from running or completed task. It is categorised as a Read tool in the MCP SSH Orchestrator MCP Server, which means it retrieves data without modifying state.
Register the MCP SSH Orchestrator MCP server in PolicyLayer and add a rule for ssh_get_task_output: 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 Orchestrator. Nothing to install.
ssh_get_task_output is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ssh_get_task_output 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_get_task_output. 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_get_task_output is provided by the MCP SSH Orchestrator MCP server (samerfarida/mcp-ssh-orchestrator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP SSH Orchestrator, 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.
13 MCP SSH Orchestrator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.