Save SSH credentials locally under a reusable name. If a password is provided, the server is contacted once to bootstrap a key and only the generated key credential is saved.
AI agents use ssh_save_credentials to create or update resources in SSH Remote MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SSH Remote MCP Server environment.
This tool creates and persists credential data (SSH keys/credentials) locally, which is a Write operation—it modifies the local credential store reversibly. Severity is high because compromised or maliciously stored credentials could grant unauthorized access to remote servers.
From the tool's definition Tool description states 'Save SSH credentials locally under a reusable name' — this creates and stores credential data. The mention of bootstrapping 'a key' and 'saving' it indicates creation and storage of authentication material.
Documented attack patterns abuse exactly the kind of access ssh_save_credentials gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SSH Remote MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ssh_save_credentials:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_save_credentials": {
"limits": [
{
"counter": "ssh_save_credentials_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ssh_save_credentials stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Save SSH credentials locally under a reusable name. If a password is provided, the server is contacted once to bootstrap a key and only the generated key credential is saved. It is categorised as a Write tool in the SSH Remote MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SSH Remote MCP Server MCP server in PolicyLayer and add a rule for ssh_save_credentials: 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 Remote MCP Server. Nothing to install.
ssh_save_credentials is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ssh_save_credentials 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_save_credentials. 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_save_credentials is provided by the SSH Remote MCP Server MCP server (nqmn/adremote-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SSH Remote 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.
21 SSH Remote MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.