Revoking an MCP Hub connection withdraws one assistant’s access while retaining its connection record and audit history. Use it when that assistant should stop working with your installation.

Choose the right scope of stop

Open PD Modules → MCP Hub → Connections. Identify the assistant by its connection name and staff account. If several assistants share its token, revocation affects all of them. Separate connections make it possible to stop one integration independently.

Revoke applies to one connection. Settings → Kill switch stops the endpoint for every connection. Choose the scope that matches the situation; a single-assistant retirement does not require stopping the whole hub.

Revoke the connection

1. Locate the active connection’s row.
2. Choose Revoke.
3. Read the confirmation explaining that anything using this token stops working, including a conversation in progress.
4. Confirm the revocation and check that the row shows Revoked.
5. Remove or disable that connection in the assistant’s settings so it does not continue attempting requests.

The old token no longer authenticates. Changing the assistant’s local display name or starting another chat does not restore it. Revocation does not undo work that completed before access was withdrawn.

Keep the evidence

Use Audit trail to review the connection’s recent calls and the revocation entry. A retained revoked connection is useful when you need to understand which assistant performed earlier work. Deleting the connection is a separate operation and is not needed to stop access.

If the assistant is needed again, plan a new authorised connection with the required staff account, areas and limits. The Connections editor does not offer an enable switch that reverses revocation, and token replacement is offered only on live connections. Do not promise that saving the old row reactivates it.

When investigating an unexpected action, reconcile its actual result before asking an assistant to repeat it. Revocation prevents subsequent access; it is not a rollback or proof that an earlier request failed.

See the PD MCP Hub Blesta guide for related tasks, or explore PD MCP Hub.