disconnect

What disconnect does on BullMQ MCP Server

AI agents use disconnect to create or update resources in BullMQ MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BullMQ MCP Server environment.

Why disconnect is rated Medium

Disconnecting from a Redis instance is a state management operation that terminates a connection but does not create, delete, or permanently alter stored data. It is reversible—the user can reconnect. While it has operational consequences (queued operations may be affected), it does not irreversibly destroy data or execute arbitrary code. Write is the appropriate category for reversible state modifications.

From the tool's definition Tool name is 'disconnect' and description states it 'Disconnect from current Redis instance'. This modifies the connection state (closes/terminates a connection), which is a reversible change to the application's runtime state rather than data persistence.

The rule that runs disconnect safely

PolicyLayer is an MCP gateway: it sits between your AI agents and BullMQ MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For disconnect, this is the rule to start with:

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

Questions about disconnect