Skip to main content
The Server Tools page in Ultra Hub is a cross-server inventory of every MCP tool your organization has used. Where the Servers page is organized by upstream server, the Server Tools page flattens that into one row per tool, so you can see every tool in one place: how heavily each is used, how often its calls are blocked, and which tools are tied to anomalies. It is the fastest way to find a specific tool across all your servers and to shut down a risky one organization-wide.
This page is the inventory of tools exposed by your upstream servers (GitHub, Linear, and so on). For Ultra’s own built-in tools — ultra_status, ultra_add, ultra_reconnect, and more — see Ultra MCP Tools.

​
Tool inventory

Each row is a unique server and tool pair. The table merges live usage stats with enforcement data: Tools that have only ever been blocked (every call denied, with no successful traffic) still appear, with zeroed stats, so a tool you blocked before it was ever used does not vanish from the inventory. Sort by any column (the default is Calls, highest first), filter by Tool name or Server, and group by tool or server. Use Export to download the inventory as CSV or JSON, and the Copy link button in a tool’s detail panel to share a deep link to it. See the dashboard guide for how export and shareable links work.

​
Tool detail

Click any row to open the tool’s detail panel. Its header carries a copy-link button and, for Hub admins, Govern and Block tool actions. Below that:
  • Overview: calls, success rate, average latency, distinct clients, and the tool’s blocked and anomaly counts.
  • Security: recent blocked calls (each with the policy that blocked it and the client behind the call, plus a link to view them in the audit log) and recent anomaly findings.
  • By client: how many calls each MCP client has made to the tool.
  • Recent calls: the latest traces for the tool, with a link to view them in Traffic.
The panel is also where you act on a single tool: use Govern to jump to its governance rules, or Block tool / Unblock tool to act on it directly.

​
Blocking a tool

Blocking is available to owners and admins in Ultra Hub. On a standalone gateway, the Server Tools page is read-only.
The Server Tools page is wired into Governance, so you can stop a tool without leaving the inventory.
  • Block a single tool from its detail panel. This creates an organization-wide governance rule that denies that tool on that server, and the row picks up a Blocked badge.
  • Block several tools at once by selecting their rows and choosing Block in the selection toolbar. A confirmation dialog summarizes how many tools will be blocked before the rules are created.
  • Unblock works the same way, individually or in bulk, for tools that a tool-level rule is blocking. Tools carrying a Server blocked badge are blocked by a server-wide rule instead; unblock those from the Servers or Governance page.
  • Govern opens the Governance page focused on the tool’s server when you need a more specific rule (particular clients, or a workspace or gateway scope) than a blanket block.
Blocks created here are ordinary governance rules: they sync to every gateway in seconds, and every decision is recorded in the audit log.

​
Use cases

  • Find a tool fast. Search the whole fleet for a tool by name instead of opening servers one at a time.
  • Spot risky tools. Sort by Blocked or Anomalies to surface the tools driving enforcement and anomaly activity.
  • Shut down a tool organization-wide. Block a dangerous or deprecated tool in one click and confirm the denials in the audit log.
  • Right-size governance. Start from a blanket block here, then narrow it to specific clients or scopes from the Governance page.

Servers

Browse upstream servers and their per-tool breakdowns

Governance

Allow and deny rules for servers, tools, and clients

Guardrails

Enforce policies on tool names, parameters, and content

Audit Log

Review every block and enforcement decision