Report the health of every MCP server proxied by Bastion: which are connected, disconnected, reconnecting, or failed; how many tools each exposes; and the last error. Call this when a tool seems to be missing or a server may have dropped mid-session.

Attempt to reconnect a disconnected or failed MCP server by name. Use this after bastion status shows a server is not connected, to restore its tools without human intervention.

Report the security state of every proxied tool: whether its definition matches what was first approved (or changed — a possible 'rug pull'), any poisoning heuristics its description triggered, and whether another server exposes a tool with the same name (shadowing).

Re-approve a tool whose definition changed, clearing a rug-pull block so it can be called again. Only do this after reviewing and trusting the change.

Report an audit/compliance summary of recent tool activity, mapped to governance frameworks (NIST AI RMF functions and OWASP LLM Top 10 categories). Requires audit to be enabled.