How to review a changed MCP server in Blesta
When a refresh detects that an attached server’s tool definitions differ from the approved set, PD MCP Hub holds that server for review. Its tools are withdrawn from the offered catalogue until a person reviews and approves the stored definitions again.
Identify the reason for the hold
Open PD Modules → MCP Hub → Attached servers. Find the server marked Changed — review and read Why and Last checked. This is different from a connection ceiling refusal or an expired hub token.
Scheduled checks run through the installation’s normal maintenance. The change is detected when a check runs; do not assume that the hub receives an immediate notification of every remote edit.
Review what is now offered
- Choose Tools & risk for the affected server.
- Read the displayed reason for the hold and the current offered tools.
- Check changed or newly offered operations against the provider’s documentation and your intended integration.
- Review each tool’s risk class; new tools begin as Dangerous, while an existing tool’s saved classification still needs review when its behaviour changes.
- Choose Approve exactly these definitions only when the whole offered set is acceptable.
The table shows the currently stored offers and shortened descriptions. It is not a complete old-versus-new definition viewer. If you cannot establish what a changed tool does, keep the server held and obtain the full definition or clarification from that server’s provider before approving the set.
Restore only the intended use
After approval, check the server state and the connections permitted to reach it. Refresh the assistant’s list and verify an authorised task. Existing connection grants and ceilings remain separate limits.
A Re-check fetches the catalogue again; it does not approve changed definitions for you. Repeated checking cannot replace the human review step. If the integration is no longer wanted, remove the server instead of accepting its new scope.
Before repeating a previously submitted write, reconcile its actual outcome at the target service. A catalogue hold prevents subsequent use through the hub; it does not roll back operations that already completed.
Check the changed definitions
Your hosting team should identify the check that detected the change and compare the current stored offers with the provider’s current tool documentation. Keep the attachment held until the whole offered set is understood and acceptable. Obtain clarification about an unclear tool definition from its provider before approving it. Reconcile any earlier write at its target before another attempt.
See the PD MCP Hub Blesta guide for related tasks, or explore PD MCP Hub.
