foundry-tool-governance

Design and govern Microsoft Foundry tool surfaces with curated, versioned, policy-controlled toolboxes.

Updated May 24, 2026
One-click install
npx skills add https://github.com/FVossebeld/agent-skills-for-context-engineering --skill foundry-tool-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foundry-tool-governance
Source: https://github.com/FVossebeld/agent-skills-for-context-engineering/tree/main/azure/skills/foundry-tool-governance
Command: npx skills add https://github.com/FVossebeld/agent-skills-for-context-engineering --skill foundry-tool-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Foundry Tool Governance solves the problem of uncontrolled and ungoverned agent tool access by shaping tool surfaces into curated, versioned, and policy-governed toolboxes.

Core Features & Use Cases

  • Curated Toolbox: expose a limited, intentional set of tools via the Foundry Toolbox.
  • Catalog governance: manage tool catalog lifecycles, versioning, and promotion across environments.
  • Policy & authentication: central governance through APIM Gateway policies, managed identities, and RBAC.
  • Use Case: ensure tool scoping and observability when teams deploy multiple tools to agents.

Quick Start

Create a toolbox with a curated set of tools and apply governance policies before making the toolbox available to agents.

Frequently Asked Questions about foundry-tool-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I govern agent tool access in Microsoft Foundry to keep it auditable?

You govern Foundry tool access by shaping tool surfaces into curated, versioned, and policy-governed toolboxes. This ensures agent tool usage remains small, deterministic, and fully auditable through explicit tool catalog boundaries.

What is a Foundry toolbox and when do I need it for policy enforcement?

A Foundry toolbox is a curated package of multiple tools exposed to agents with enforced governance policies. You need it when deploying multiple tools to agents and must ensure tool scoping, observability, and explicit catalog boundaries.

How do I set up RBAC and authentication integration for a Foundry tool catalog?

You set up RBAC and authentication for a Foundry tool catalog by applying central governance through APIM Gateway policies and managed identities. This enforces policy boundaries and authentication integration across tool usage.

Can I manage tool versioning and promotion across environments using Foundry governance?

Yes, you can manage tool catalog lifecycles, versioning, and promotion across environments using Foundry governance. It applies governance policies to ensure deterministic tool access and observed policy enforcement during promotion.

What is the best way to scope tools for agents to prevent uncontrolled access?

The best way to scope tools is by packaging multiple tools into a curated Foundry toolbox with explicit catalog boundaries. Applying governance policies before exposing the toolbox keeps agent tool access small and deterministic.

Does Foundry tool governance require APIM Gateway to enforce policy?

Foundry tool governance uses APIM Gateway policies to apply central governance through managed identities and RBAC. This integration enforces observed policy boundaries and authentication integration across all tool usage.