ssh_remove_job
AI agents call ssh_remove_job to permanently remove resources in Mcp Ssh Live — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name 'remove_job' indicates deletion of job state or records on a remote SSH server. While the empty description creates some ambiguity about whether removal is reversible (archive vs. purge), in the context of SSH job management systems, job removal typically cannot be undone.
From the tool's definition Tool name 'ssh_remove_job' from ssh_list_jobs and ssh_run_persistent sibling context; removes/deletes job records, likely irreversibly. Description is empty, limiting confidence.
Attacks that exploit this kind of access
ssh_remove_job. It is categorised as a Destructive tool in the Mcp Ssh Live MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Ssh Live MCP server in PolicyLayer and add a rule for ssh_remove_job: 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_remove_job is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ssh_remove_job 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_remove_job. 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_remove_job 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 →