ssh_setup_key_auth

THE RISK

Medium Risk

Why ssh_setup_key_auth needs a policy

This tool creates new cryptographic material (keypair generation) and modifies remote server state (installing public key and saving credentials). While it doesn't delete data or execute arbitrary commands, it does irreversibly modify authentication infrastructure in a way that could enable persistent unauthorized access if misused.

From the tool's definition Tool description states it will 'Generate a local SSH keypair, install the public key on the remote server, and save a key-based credential for future connections' — this creates and modifies authentication credentials and remote server configuration.

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

POLICY

How to control ssh_setup_key_auth

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_setup_key_auth:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ssh_setup_key_auth": {
      "limits": [
        {
          "counter": "ssh_setup_key_auth_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

ssh_setup_key_auth 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.

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

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More SSH Remote MCP Server tools

Destructive ssh_delete_saved_credentials Delete a saved local SSH credential entry Execute ssh_execute Execute a command on a remote SSH connection Execute ssh_execute_plan Execute an approved command or remote file edit plan Execute ssh_approve_plan Approve a stored plan so it can be executed Execute ssh_connect Connect to a remote Ubuntu server via SSH Execute ssh_connect_saved Connect to a remote server using a saved local SSH credential name Execute ssh_plan_command Create a reviewed execution plan for a non-trivial remote command Write ssh_plan_edit Create a managed remote file edit plan that requires approval before writing

All 21 SSH Remote MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about ssh_setup_key_auth

What does the ssh_setup_key_auth tool do? +

Generate a local SSH keypair, install the public key on the remote server, and save a key-based credential for future connections. 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.

How do I enforce a policy on ssh_setup_key_auth? +

Register the SSH Remote MCP Server MCP server in PolicyLayer and add a rule for ssh_setup_key_auth: 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.

What risk level is ssh_setup_key_auth? +

ssh_setup_key_auth is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ssh_setup_key_auth? +

Yes. Add a rate_limit block to the ssh_setup_key_auth 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 ssh_setup_key_auth completely? +

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

ssh_setup_key_auth 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.

Enforce policy on every SSH Remote MCP Server tool call.

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.

CHECK YOUR STACK →