Low Risk

getConnection

Gets detailed information about a specific SSH connection.

How to control getConnection ↓

AI agents call getConnection to retrieve information from Mcp Ssh without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and retrieves metadata about an existing SSH connection without performing any side effects, modifying data, executing commands, or creating/destroying resources. It is a straightforward Read operation. While the server as a whole exposes Execute and Destructive capabilities (executeCommand, deleteConnection), this specific tool is limited to information retrieval.

From the tool's definition Tool name is 'getConnection' and description states it 'Gets detailed information about a specific SSH connection' — a pure retrieval operation with no modification or execution.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ssh, and nothing reaches the server without passing your rules. This is the rule we recommend for getConnection:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getConnection": {}
  }
}

getConnection is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Ssh — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the getConnection tool do? +

Gets detailed information about a specific SSH connection. It is categorised as a Read tool in the Mcp Ssh MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getConnection? +

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

What risk level is getConnection? +

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

Can I rate-limit getConnection? +

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

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

getConnection is provided by the Mcp Ssh MCP server (shuakami/mcp-ssh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ssh tool call.

Deterministic rules across all 23 Mcp Ssh tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

23 Mcp Ssh tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.