add_ssh_key
Register a new SSH public key with policy checks.
This record as markdown: /tools/bhayanak-ssh-mcp-server/add-ssh-key.md
What add_ssh_key does on SSH MCP Server
AI agents use add_ssh_key to create or update resources in SSH MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SSH MCP Server environment.
Why add_ssh_key is rated Medium
Adding SSH keys modifies the authentication system and grants access, but the operation is reversible (keys can be removed). It falls under Write rather than Execute because it's not running commands or scripts. However, severity is high because misconfigured SSH key additions could grant unauthorized access to remote systems. The 'policy checks' mention suggests some safeguards exist, preventing critical rating.
From the tool's definition Tool name 'add_ssh_key' and description 'Register a new SSH public key with policy checks' indicate creation/modification of SSH authentication credentials. This is a write operation that creates new security material.
Attacks that exploit this kind of access
The rule that runs add_ssh_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SSH MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_ssh_key, this is the rule to start with:
add_ssh_key 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.
The button opens the PolicyLayer dashboard: create your workspace, connect SSH MCP Server, apply this rule, and every add_ssh_key call is checked against it from then on.
Questions about add_ssh_key
Register a new SSH public key with policy checks. It is categorised as a Write tool in the SSH MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for add_ssh_key: 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.
add_ssh_key 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 add_ssh_key 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 add_ssh_key. 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.
add_ssh_key is provided by the SSH MCP Server MCP server (bhayanak/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SSH MCP Server, and thousands of servers like it.
This server
Across the catalogue