ssh_health_check

THE RISK

Low Risk

Why ssh_health_check needs a policy

A health check tool reads the current state of SSH connections and reports their status. It does not create, modify, delete, or execute anything on remote systems. The blast radius if misused is minimal — at most it reveals connection metadata.

From the tool's definition "Check the health of SSH connections" — purely diagnostic/status query with no side effects

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

POLICY

How to control ssh_health_check

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ssh_health_check": {}
  }
}

ssh_health_check is read-only, so it stays allowed — but 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.

CAP 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 →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about ssh_health_check

What does the ssh_health_check tool do? +

Check the health of SSH connections. It is categorised as a Read tool in the SSH Remote MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ssh_health_check? +

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

ssh_health_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ssh_health_check? +

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

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

ssh_health_check 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 →