Use Audit trail to check what an MCP Hub assistant requested, whether it was allowed and why it was refused or failed. It is useful for confirming a connection change or investigating a particular operation.

Find the relevant entries

1. Open PD Modules → MCP Hub → Audit trail.
2. Identify the intended connection and the time of the request.
3. Read the tool, outcome and detail together; do not rely only on the assistant’s wording.
4. Use the outcome selector to switch between Everything, Allowed, Refused, Sent for approval and Failed.
5. Return to Everything when you need to follow the sequence around an event.

The visible table shows recent entries. Its summary counts describe recent activity, while the retained history can extend further. A filtered or recent view is not evidence that no older request occurred.

Interpret the outcome

Allowed records an executed tool call, not proof that every downstream business outcome has completed. Refused means an access check stopped that request. Sent for approval means a decision is still needed rather than an operation already performed. Failed needs its error detail reviewed before any retry.

For a pending approval, inspect Approvals, including what the request will do and what the assistant had just read. Do not ask the assistant to submit repeated alternatives merely to clear a pending item.

Export and retain the evidence

Use Download the whole trail as CSV when you need the retained record beyond the visible recent table. Store the export appropriately: redaction removes recognised sensitive arguments, but a trail can still contain operational details and client references. Do not publish the export or attach it unreviewed to a public discussion.

Settings → Keep the audit trail for (days) controls retention; normal maintenance removes older entries. An export cannot restore entries already removed.

If a connection attempt has no matching entry, check endpoint state, the selected outcome filter and the reported response before blaming the network. A disabled endpoint can refuse before recording a connection, and missing audit data alone does not prove that a firewall blocked the request.

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