gateway.disconnect_server

THE RISK

Critical Risk

Why gateway.disconnect_server needs a policy

Disconnecting a running server terminates an active connection and stops the downstream MCP server's operation. This is effectively irreversible at the moment of action — the running server process/session is torn down.

From the tool's definition Disconnect a running downstream MCP server without changing persistent config

Documented attack patterns abuse exactly the kind of access gateway.disconnect_server gives an agent:

POLICY

How to control gateway.disconnect_server

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "gateway.disconnect_server"
  ]
}

gateway.disconnect_server disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register PMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More PMCP tools

Execute gateway.tasks_cancel Cancel a downstream MCP task by opaque task ID. Execute gateway.connect_server Connect or start a known downstream MCP server by name. Execute gateway.invoke Invoke a tool on a downstream MCP server. Execute gateway.provision Provision (install and start) a specific MCP server from the manifest. Execute gateway.restart_server Restart a known downstream MCP server without changing persistent config. Execute gateway.refresh Reload backend MCP server configurations and reconnect. Execute gateway.request_capability Find and auto-provision the right tool for a task — describe what you need in natural lang Write gateway.cancel Cancel a pending tool invocation.

All 26 PMCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in PMCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about gateway.disconnect_server

What does the gateway.disconnect_server tool do? +

Disconnect a running downstream MCP server without changing persistent config. It is categorised as a Destructive tool in the PMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on gateway.disconnect_server? +

Register the P MCP server in PolicyLayer and add a rule for gateway.disconnect_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 PMCP. Nothing to install.

What risk level is gateway.disconnect_server? +

gateway.disconnect_server is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gateway.disconnect_server? +

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

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

gateway.disconnect_server is provided by the P MCP server (viperjuice/pmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PMCP tool call.

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

CHECK YOUR STACK →