Tool access

This capability is on the Roadmap; the API shown here is the planned design.

Governed tool access lets an agent discover the MCP tools your organisation has published and governed, filter them down to what it actually needs, and bind them into any of the eight supported frameworks as that framework’s native tool objects — the same “no wrapper” approach as model access.

Two lines from catalog to agent

tools = await donkey.tools.discover(domain="hr", tags=["approved"])
agent = create_react_agent(donkey.langgraph.chat_model("gpt-4o"), tools.langgraph())

Everything else in this section — search filters, session management, per-framework binding, pinning, and A2A tool handles — makes those two lines hold up in production.

Discover and filter

donkey.tools.discover(...) is also the search and filter entry point. One call narrows the catalog by name/description glob, governance, domain, tags, and asset type, so an agent binds only the tools it needs:

tools = await donkey.tools.discover(
    search="*accounts*",     # glob over asset name + description
    governed_only=True,      # default criteria, or a GovernanceCriteria
    domain="hr",
    tags=["approved"],
    asset_types=["mcp"],
    environment="Production",
    limit=50,
)

“Governed” is a computed, environment-scoped predicate rather than a flag in Exchange — see Discovery, search & filter.

In this section