refresh_connections

Server SSH MCP Server termau/ssh-mcp

Category Write

Risk class Medium

Parameters 00 required

WHAT IT DOES

What refresh_connections does on SSH MCP Server

AI agents use refresh_connections 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 IT NEEDS A POLICY

Why refresh_connections needs a policy

An AI agent can call refresh_connections faster than any human can review — one bad instruction and it creates or modifies resources in SSH MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_connections Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SSH MCP Server, so you can run agents against it safely.

FAQ

Questions about refresh_connections

What does the refresh_connections tool do? +

Re-discover BinaryLane servers and reload all connections. Refreshes the connection list by: 1. Re-reading the config file 2. Re-discovering BinaryLane servers (if enabled) 3. Re-reading SSH_CONNECTIONS env var 4. Merging all sources (config > env > auto-discovered) Use after creating/deleting BinaryLane servers to update the connection list. 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.

How do I enforce a policy on refresh_connections? +

Register the SSH MCP Server MCP server in PolicyLayer and add a rule for refresh_connections: 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 refresh_connections? +

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

Can I rate-limit refresh_connections? +

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

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

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