ssh_test

Test SSH connectivity to a configured profile. Returns latency and server version.

SERVERTerminal Guardian SOURCE7majesty-m/terminal-guardian-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/7majesty-m-terminal-guardian-mcp/ssh-test.md

WHAT IT DOES

What ssh_test does on Terminal Guardian

AI agents invoke ssh_test to trigger actions in Terminal Guardian. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why ssh_test is rated High

Testing SSH connectivity requires actually establishing (or attempting to establish) a network connection to a remote server. This is an Execute-class action because it triggers an external network operation. While it only reads back latency and server version (suggesting read-like intent), the act of initiating an SSH handshake has side effects on external systems (logging on the remote, consuming resources).

From the tool's definition 'Test SSH connectivity to a configured profile' — initiates an active SSH connection attempt to a remote host

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ssh_test safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Terminal Guardian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ssh_test, this is the rule to start with:

ssh_test Rate-limited

ssh_test stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ssh_test": {
      "limits": [
        {
          "counter": "ssh_test_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Terminal Guardian, apply this rule, and every ssh_test call is checked against it from then on.

FAQ

Questions about ssh_test

What does the ssh_test tool do? +

Test SSH connectivity to a configured profile. Returns latency and server version. It is categorised as a Execute tool in the Terminal Guardian MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ssh_test? +

Register the Terminal Guardian MCP server in PolicyLayer and add a rule for ssh_test: 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 Terminal Guardian. Nothing to install.

What risk level is ssh_test? +

ssh_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ssh_test? +

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

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

ssh_test is provided by the Terminal Guardian MCP server (7majesty-m/terminal-guardian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Terminal Guardian, and thousands of servers like it.

This server

All 25 Terminal Guardian tools → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →