Open an SSH session to the given machine and track it in global state so subsequent tool calls can reuse it.
AI agents invoke create_connection to trigger actions in SSH MCP Server. 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.
Creating an SSH connection is not merely storing data (Write); it establishes an active network session to a remote system, which is an external operation with real side effects. It enables all subsequent Execute/Destructive operations on remote machines.
From the tool's definition 'Open an SSH session to the given machine and track it in global state so subsequent tool calls can reuse it' — establishes live SSH connectivity to remote systems, enabling all subsequent command execution
Attacks that exploit this kind of access
Open an SSH session to the given machine and track it in global state so subsequent tool calls can reuse it. It is categorised as a Execute tool in the SSH MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for create_connection: 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.
create_connection is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_connection 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.
Set action: deny in the PolicyLayer policy for create_connection. 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.
create_connection is provided by the SSH MCP Server MCP server (vilasone455/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →