ssh_list_jobs
AI agents call ssh_list_jobs to retrieve information from Mcp Ssh Live without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or query the status of SSH jobs spawned by the server, which is a read-only operation. However, confidence is moderate rather than high because the description is empty and the tool could theoretically expose sensitive information about running processes or command execution history across multiple hosts.
From the tool's definition Tool name 'ssh_list_jobs' indicates a listing/query operation with no description provided. Sibling tools include 'ssh_exec', 'ssh_run_persistent', 'ssh_remove_job', 'ssh_send_stdin', 'ssh_signal' which perform state-changing operations; by contrast, 'list'…
Attacks that exploit this kind of access
ssh_list_jobs. It is categorised as a Read tool in the Mcp Ssh Live MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ssh Live MCP server in PolicyLayer and add a rule for ssh_list_jobs: 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 Live. Nothing to install.
ssh_list_jobs 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_list_jobs 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_list_jobs. 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_list_jobs is provided by the Mcp Ssh Live MCP server (pmboxbiz/mcp-ssh-live). 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 →