Medium Risk

disconnectServer

Disconnects from a dynamically connected agent server and removes it from the proxy

How to control disconnectServer ↓

What disconnectServer does on Mcp Agent Proxy

AI agents use disconnectServer to create or update resources in Mcp Agent Proxy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Agent Proxy environment.

Medium Risk

Why disconnectServer needs a policy

The tool modifies internal proxy state by disconnecting and removing a server connection. This is a reversible write operation (the server can be reconnected later via connectServer) rather than destructive deletion of underlying data. The severity is medium because disrupting agent network connectivity could break dependent workflows, but the effect is reversible and scoped to connection state management.

From the tool's definition Tool name is 'disconnectServer' and description states it 'Disconnects from a dynamically connected agent server and removes it from the proxy'. This modifies the proxy state by removing a server connection.

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

How to control disconnectServer

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "disconnectServer": {
      "limits": [
        {
          "counter": "disconnectserver_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

disconnectServer stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Agent Proxy — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about disconnectServer

What does the disconnectServer tool do? +

Disconnects from a dynamically connected agent server and removes it from the proxy. It is categorised as a Write tool in the Mcp Agent Proxy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disconnectServer? +

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

What risk level is disconnectServer? +

disconnectServer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disconnectServer? +

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

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

disconnectServer is provided by the Mcp Agent Proxy MCP server (mashh-lab/mcp-agent-proxy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Agent Proxy tool call.

Start from Mcp Agent Proxy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

5 Mcp Agent Proxy tools catalogued and risk-classified — across an index of 43,000+ 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.