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 filter entry point. One call narrows the catalog by governance, domain and tags, so an agent binds only the tools it needs:

tools = await donkey.tools.discover(
    domain="hr",
    tags=["approved"],
    governed=True,           # default criteria, or a GovernanceCriteria
)

Name search, asset type and environment filters live one layer down, on donkey.registry.search().

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

In this section