Registering a Resource Behind a Gateway
Last Modified: 2026-11-19

Registering a Resource Behind a Gateway

A resource is anything an agent can reach through a gateway: an MCP server or a REST API described by an OpenAPI specification.

Tool TypeHow It Is Added
MCP serversRegister the server's address. Before you save it, the gateway connects to the server and lists its tools, so you can see exactly what you are adding.
REST APIsImport the API's OpenAPI (Swagger) description. The gateway turns each operation into a tool, you review them, and expose only the ones you approve.

Some tools need each person to sign in with their own account. In that case, the person signs in to the tool once through the gateway, and the gateway uses that sign-in on their behalf from then on.

Note:  Agent ID runs tool discovery automatically from the OpenAPI specification or MCP server you point it at, suggesting a privilege level for each discovered operation so you do not have to classify every tool by hand.

The Resources page has two tabs, All resources and Secured resources. A banner at the top of the page shows how many changes to connected resources are pending publication, with a Go to Publish management link.

Register resource appears only on the Secured resources tab, and only when your subscription includes Agent ID Secure.

The Resources page opens with a Resource summary showing Total resources, how many are Registered (with the percentage of inventory that represents), and how many are Shadow and need review. The table on the Resources page lists every discovered and registered resource, with the columns Resource/namespace, Type (MCP server, API, or Tool endpoint), Status (Shadow, Under review, or Registered), Tools (count discovered), Transport (for example, http or stdio), Owner, Runtime, Tags, Last seen holding it, and Reached by:. Filter the list by Resource/namespace, Type, Status, or Advanced filters. Click Export to download the table. A shadow resource found here is the same kind of finding surfaced on Triaging Shadow Assets; registering it from either page has the same effect.

Procedure 

  1. On the Resources page, open the Secured resources tab and click Register resource.

  2. Under Source, select the server type: MCP server (tools are discovered live) or REST API (OpenAPI). Each operation in the spec becomes a tool.

  3. Under Gateway runtimes, select the gateways that should route to the resource (use Select all to choose every gateway), or leave it set to Unassigned, the default, so that the resource is registered and governed but not routed by any gateway.

  4. Enter a Server name (for example, DeepWiki), a short Namespace (for example, deepwiki—use lowercase letters, numbers, and hyphens; this cannot be changed after it is created), and the resource’s Endpoint URL (for example, https://mcp.deepwiki.com/mcp). Select the Transport (HTTP (SSE), HTTP (streamable), or stdio) and, optionally, type a Description.

  5. Under Connection type, choose how the gateway signs in to the resource: Per-user credentials (each person authenticates individually) or Shared credentials (one service account is used for all users).

  6. Under Authorization method, choose No authorization if the server needs no sign-in, Bearer token to use one API key or token for everyone, or OAuth so each person or agent signs in with their own account. Complete the fields for your selection:

    • OAuth: select STATIC and type the Authorize URL, Token URL, and Client ID, and optionally a Client secret and Resource URL; or select DISCOVER to autofill these details from the server’s protected resource metadata.

    • Bearer token: enter the Headers as a flat JSON object.

  7. Click Discover tools.

  8. On the Tools step, review the discovered tools. Select the ones to onboard (use Select all or Deselect all, or search the list). Each tool shows a Privilege level (LOW, MEDIUM, or HIGH) that Agent ID suggests, and you can edit; to change several tools at once, select them, choose a privilege level, and click Apply to the selected tools.

  9. Click Next: Configure scopes, then review the Endpoint scope and the Tools · scope mapping (Backend resource scope, Privilege, and Rate limit (/min) for each tool) before activation. To set one rate limit for several tools, enter a default rate limit and click Apply to the selected tools.

  10. Click Next: Verify & activate, review the connection summary (Tools, Scopes granted, Privilege mix, Rate limit, Source type, Namespace, Connection, Gateway runtimes, and Reachability), then click Activate server.

Results 

The resource appears in the Resources table with its tool count and transport, and its tools become available to agents on their next calls and to assign to roles (see Roles and Scopes), once published to its gateways (see Publishing Configuration Changes).

Managing a Resource from the Actions Menu

Select a resource in the table to open its detail panel, then click Actions to choose Edit registration, Mark for review, Assign owner (or Reassign owner), or Block.

Block requires a Reason; the block appears in Blocked agents and is not enforced until the gateway accepts it.