ssh-test

Tests SSH connectivity to a remote host using

SERVERGit SOURCEDave-London/Pare

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/io-github-dave-london-git/ssh-test.md

WHAT IT DOES

What ssh-test does on Git

AI agents invoke ssh-test to trigger actions in Git. 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 involves executing a network connection attempt to a remote host. This is an external operation with side effects (network traffic, authentication attempts) that goes beyond simple data retrieval. The description is truncated, which reduces confidence slightly, but 'SSH connectivity' testing implies executing a connection.

From the tool's definition 'Tests SSH connectivity to a remote host using' — initiates an outbound SSH connection to an external 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 Git, 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 Git, 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? +

Tests SSH connectivity to a remote host using. It is categorised as a Execute tool in the Git 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 Git 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 Git. 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 Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 202 Git 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 →