connect_to_server · MCP Test MCP: Risk & Policy

WHAT IT DOES

What connect_to_server does on MCP Test MCP

AI agents invoke connect_to_server to trigger actions in MCP Test 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_to_server needs a policy

Based on the server description, this tool likely establishes a connection to an external MCP server, which is an external operation with side effects. Connecting to external servers can expose systems to network-level risks and is a prerequisite for further operations like executing tools on those servers.

From the tool's definition Tool name 'connect_to_server' on a server described as a 'testing harness that enables AI assistants to thoroughly test other MCP servers by connecting to them'. The description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_to_server Rate-limited

connect_to_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_to_server": {
      "limits": [
        {
          "counter": "connect_to_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 MCP Test MCP, so you can run agents against it safely.

FAQ

Questions about connect_to_server

What does the connect_to_server tool do? +

connect_to_server. It is categorised as a Execute tool in the MCP Test 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_to_server? +

Register the MCP Test MCP server in PolicyLayer and add a rule for connect_to_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 MCP Test MCP. Nothing to install.

What risk level is connect_to_server? +

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

Can I rate-limit connect_to_server? +

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

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

connect_to_server is provided by the MCP Test MCP server (rdwj/mcp-test-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.