Tools

Tools is the inventory your MCP routes publish from: tools imported from the MCP servers you connected, and tools backed by your own endpoints. It also watches imported tools for changes, so a tool that changes upstream is taken out of service until you review it.


Connected MCP Servers

The top of AI runtime → Tools lists the servers you connected, with their state and catalog.

ByteHide AI Runtime Tools screen listing connected MCP servers with Connected, Per-user and Needs authorization statesClick to expand

See Connect an MCP Server for the states and actions of each server.


Tool Inventory

Below the servers, the table lists every tool. Filter it with the search box and the All, Own and Imported toggle.

ByteHide AI Runtime tool inventory with three active tools imported from DeepWiki and the route that publishes themClick to expand

ColumnDescription
StatusActive (served), Stale (changed upstream, not served until reviewed) or Disabled (switched off, not served)
ToolTool name and description. Two tools from different servers can share a name
OriginYour own endpoint, or the server it was imported from
EndpointWhere calls go. Imported tools go via its server
Used in routesThe MCP routes that publish it

Own Tools

Click Add Tool to publish a tool backed by your own HTTP endpoint. Its schema is validated when you save. Own tools can be edited and deleted.


Imported Tools and Drift

Imported tools stay tied to their server. They cannot be edited or deleted by hand: editing one would make drift detection compare your edits against the upstream. To update them, run discovery and re-import.

Every discovery compares the server's current catalog with what you imported. When a tool's definition changed, the tool becomes Stale.

A stale tool is out of service

A Stale tool still appears in catalogs, but every call to it is refused until someone reviews the change and clicks Re-import. This protects your agents from a tool whose definition was swapped after you approved it.

If a tool disappears upstream, it comes back automatically when the server serves it again: run discovery instead of recreating it.


Actions

ActionEffect
Run discoveryFetches the server's catalog and checks imported tools for drift
ImportAdds tools from a discovered catalog
Re-importAccepts a changed schema and puts a stale tool back in service
Enable / disableSwitches a tool on or off. Disabled tools are not served
DeleteRemoves an own tool

Next Steps

MCP Protection

Publish tools on an MCP route

MCP Incidences

See every call to every tool

Previous
Per-user Connections