Skip to main content
Tool-management tools register the MCP servers that Gateways proxy for agents. Each connection represents an upstream MCP server agents access through Dome. These tools require workspace context. For Gateway membership and access grants, refer to Gateways. For LLM model connections, refer to Models.

Tool CRUD

dome_tool_list

List MCP server connections in the active workspace. Returns name, URL, protocol, auth method, outbound headers, and field classifications for each. Permission: gateway.view
Example tool call

dome_tool_get

Get an MCP server connection by name. Permission: gateway.view

dome_tool_add

Add a new MCP server connection. Connections route the gateway to external MCP servers agents reach through Dome. Permission: gateway.manage The oauth object accepts: When auth_method=oauth and credential_type=shared, the response includes oauth_connect_url — open it in a browser to complete consent.
Shared OAuth tool

dome_tool_update

Update an existing MCP server connection. Only provided fields are changed. Permission: gateway.manage Switching auth_method between api-key and oauth clears the previously stored credential bundle.

dome_tool_oauth_connect

Begin the shared-OAuth admin consent flow for a tool. Returns a one-shot URL the operator opens in a browser to consent at the upstream’s authorization server. Only valid for auth_method=oauth, credential_type=shared. Per-user OAuth tools trigger consent automatically on each end user’s first call. Permission: gateway.manage The response includes oauth_connect_url and oauth_connect_expires_at. Open the URL within ~10 minutes.

dome_tool_oauth_disconnect

Disconnect (revoke) shared OAuth credentials. The OAuth client configuration is preserved, so re-running connect reuses the same client. Idempotent. Marked destructive. Permission: gateway.manage

dome_tool_remove

Remove an MCP server connection from the active workspace. Marked destructive. Permission: gateway.manage
Removing a tool disconnects all agents currently routing through it. Update or re-route agents first.

Tool Catalog

dome_tools_for_connection

List the operations Dome has discovered on one MCP server connection. This reads the stored catalog and does not apply Gateway membership or agent rules. Permission: gateway.view
List discovered operations

Tool Lifecycle

Transition individual MCP tools (the items inside a connection’s catalog) through activedeprecatedblocked. Status persists across re-observation — once set, only an explicit restore returns the tool to active.

dome_tool_block

Hide an MCP tool from agents. The Gateway filters it out of tools/list and denies any tools/call against it; blocked-call attempts emit a tool.blocked_call_denied audit event. A block takes precedence over ordinary connection-level access. Permission: gateway.manage
Block a dangerous tool

dome_tool_deprecate

Mark a tool as deprecated. The tool stays callable and visible to agents — the dashboard surfaces a warning chip and the status flows through the catalog. Use when an upstream supersedes a tool and you want to soft-signal callers. Permission: gateway.manage

dome_tool_restore

Restore a tool to active, clearing any prior block or deprecation. Permission: gateway.manage

Next steps

Attach backends under Connect. Named Gateways and grants are a separate tool group: