Delete a saved SSH credential
AI agents call ssh_delete_credential to permanently remove resources in MCP SSH Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a saved credential is irreversible; once removed, the credential configuration is gone and cannot be recovered without re-entering it. This falls squarely in the Destructive category. Severity is medium because while it doesn't directly destroy remote systems, losing credentials could lock out access to remote servers or disrupt automated workflows.
From the tool's definition 'Delete a saved SSH credential' — permanently removes stored credential data
Attacks that exploit this kind of access
Delete a saved SSH credential. It is categorised as a Destructive tool in the MCP SSH Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP SSH Server MCP server in PolicyLayer and add a rule for ssh_delete_credential: 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 Server. Nothing to install.
ssh_delete_credential 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_delete_credential 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_delete_credential. 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_delete_credential is provided by the MCP SSH Server MCP server (mahathirmuh/mcp-ssh-server). 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 →