connect_server · Remote Terminal MCP: Risk & Policy

WHAT IT DOES

What connect_server does on Remote Terminal MCP

AI agents invoke connect_server to trigger actions in Remote Terminal MCP. 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.

WHY IT NEEDS A POLICY

Why connect_server needs a policy

Connecting to a remote server establishes an active network session that triggers external operations and opens a channel for further command execution. While the connection itself doesn't delete data, it is a prerequisite for arbitrary remote control and represents a significant security boundary crossing.

From the tool's definition 'Connect to a remote server' — initiates an active SSH/remote session to an external system

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_server Rate-limited

connect_server 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": {
    "connect_server": {
      "limits": [
        {
          "counter": "connect_server_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Remote Terminal MCP, so you can run agents against it safely.

FAQ

Questions about connect_server

What does the connect_server tool do? +

Connect to a remote server. It is categorised as a Execute tool in the Remote Terminal MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on connect_server? +

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

What risk level is connect_server? +

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

Can I rate-limit connect_server? +

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

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

connect_server is provided by the Remote Terminal MCP server (maricoxu/remote-terminal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.