Chapter 1 of 6
Module scope#
What we will do#
Objective. Give agent teams one reusable, approval-gated endpoint for an approved MCP tool.
Connect an approved remote MCP server in Azure API Center to a dedicated versioned Toolbox in Microsoft Foundry: discover and configure the server through the API Center private tool catalog in Foundry Tools, then create a Toolbox version that exposes the approved tool and requires approval for every call. The check calls tools/list on the version-specific Toolbox MCP endpoint; the response contains exactly the approved namespaced tool.
Why it matters#
Problem. Agent teams need one shared, governed way to consume an approved MCP tool. Without one, each team wires its own connection and repeats the same access decisions.
Solution. This module turns those approved records into one reusable Toolbox endpoint. Preflight and the live check stop if the API Center deployment endpoint, Foundry project connection, allow list, or Toolbox result ever differs from the approved record.
Boundaries#
This work handles the MCP server record in API Center, the related Foundry project connection, a new dedicated Toolbox, and the approved MCP tool in an approved nonproduction scope. It uses the public-preview private tool catalog in Foundry Tools; record that preview decision before creating a Toolbox.
Azure API Center holds the inventory record and deployment metadata. The MCP server defines tools available at runtime. The Foundry project connection stores runtime authentication settings. The Toolbox version records the allowed tool and approval setting.
The MCP server and its authorization model exist before this work. The dedicated Toolbox contains the approved MCP tool and supplies its endpoint for agent reuse. API Center access controls catalog discovery, while MCP tool security guide runtime controls authorize each call. Agent owners integrate the endpoint through Governed agent baseline guide.
Module preparation
Who should join
- Azure API Center and Microsoft Foundry platform engineers
- Agent and MCP tool owners
- Security and release owners responsible for reusable agent tools
What you need
- Session 04 has an approved Microsoft Foundry project, and an agent owner is ready to use a Toolbox endpoint.
- Session 07 has an approved remote MCP server in Azure API Center with a version, deployment, runtime URL, owner, lifecycle state, and authentication decision.
- Session 08 has approved the MCP server's tool surface, authentication boundary, and runtime safety controls.
- The module operator has Azure API Center Data Reader on the exact API Center resource, Foundry User on the exact Foundry project, and Foundry Project Manager when a project connection must be created.
- The approved execution host has Azure CLI, Azure Developer CLI 1.27.1 or later, the microsoft.foundry extension, Python 3, and network access to the Foundry project and MCP server.