Critical Risk →

remove_credential

Remove a stored SSH credential

How to control remove_credential ↓

What remove_credential does on SSH MCP Server

AI agents call remove_credential to permanently remove resources in SSH MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why remove_credential needs a policy

This tool permanently deletes a stored SSH credential. Removal of credentials is irreversible and could lock out access to remote systems or disrupt automated workflows that depend on those credentials, making it a destructive action with high blast radius.

From the tool's definition Remove a stored SSH credential

Documented attack patterns abuse exactly the kind of access remove_credential gives an agent:

How to control remove_credential

PolicyLayer is an MCP gateway — it sits between your AI agents and SSH MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_credential:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_credential"
  ]
}

remove_credential disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register SSH MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about remove_credential

What does the remove_credential tool do? +

Remove a stored SSH credential. It is categorised as a Destructive tool in the SSH MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_credential? +

Register the SSH MCP Server MCP server in PolicyLayer and add a rule for remove_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 SSH MCP Server. Nothing to install.

What risk level is remove_credential? +

remove_credential is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_credential? +

Yes. Add a rate_limit block to the remove_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.

How do I block remove_credential completely? +

Set action: deny in the PolicyLayer policy for remove_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.

What MCP server provides remove_credential? +

remove_credential is provided by the SSH MCP Server MCP server (kinothe-kafkaesque/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SSH MCP Server tool call.

Start from SSH MCP Server, 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.

15 SSH MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.