disconnect_all · MCP Universal DB Client MCP: Risk & Policy

WHAT IT DOES

What disconnect_all does on MCP Universal DB Client

AI agents use disconnect_all to create or update resources in MCP Universal DB Client — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Universal DB Client environment.

WHY IT NEEDS A POLICY

Why disconnect_all needs a policy

Disconnecting all active database connections modifies system state by terminating running connections, which is a write-class operation. The blast radius is medium because it could disrupt legitimate database operations and sessions, but the effect is reversible—connections can be re-established without data loss.

From the tool's definition Tool name 'disconnect_all' and description 'Disconnect all active database connections' indicate a modification of system state—terminating active connections is a write operation that changes the state of database resources, though it is reversible…

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disconnect_all Rate-limited

disconnect_all 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "disconnect_all": {
      "limits": [
        {
          "counter": "disconnect_all_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 Universal DB Client, so you can run agents against it safely.

FAQ

Questions about disconnect_all

What does the disconnect_all tool do? +

Disconnect all active database connections. It is categorised as a Write tool in the MCP Universal DB Client MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disconnect_all? +

Register the MCP Universal DB Client MCP server in PolicyLayer and add a rule for disconnect_all: 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 Universal DB Client. Nothing to install.

What risk level is disconnect_all? +

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

Can I rate-limit disconnect_all? +

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

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

disconnect_all is provided by the MCP Universal DB Client MCP server (izumisy/mcp-universal-db-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.