An attached MCP server’s tools need review before you allow an assistant to use them. PD MCP Hub initially treats new attached tools as Dangerous rather than trusting the server’s own claim about risk.

Open the review screen

Go to PD Modules → MCP Hub → Attached servers and choose Tools & risk for the intended server. Read Appears as, What it says it does, Treated as, Noticed and State.

Descriptions in the table can be shortened. The displayed description is not a full input-schema viewer or a complete comparison with every earlier definition. Use the provider’s current documentation and your approved scope to understand the operation. If the information available is insufficient, do not approve it merely to make the connection work.

Assign the appropriate class

1. Identify the exact tool and the service it affects.
2. Read any scanner finding in Noticed, including wording about reading files or sending data elsewhere.
3. Check whether the tool genuinely only reads, changes data or performs a more consequential action.
4. Use the row’s Read, Write or Dangerous control according to the operation you have verified.
5. Review the other offered tools before choosing Approve exactly these definitions.

Do not mark a write as Read to fit a read-only connection. A scanner flag needs human review; the absence of a flag is not a guarantee that the tool is harmless. Tools refused outright by the module are not made available by changing another tool’s class.

Understand approval scope

The approval button accepts the stored offered definitions as a set. The reviewed form does not provide a separate per-tool exclude checkbox, so do not assume you have approved only the row you last clicked. When that set includes tools you cannot authorise, leave it unapproved and review the server arrangement.

Check connection access separately

Approval makes definitions eligible for use. Each connection still needs the attached-server grant and a ceiling that reaches the assigned risk. Refresh the assistant’s tool list after approved changes and inspect Audit trail for any refusal. A risk-setting success message alone is not proof that every connection may run the tool.

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