TL;DR: Policy-curated tools can cut AI agent token usage by returning only authorised tools instead of the full enterprise catalog, according to KeyRunner. It narrows discovery and makes policy scope easier to audit before execution.
Editorial analysis by NHI Mgmt Group, based on content published by KeyRunner: “How Policy-Curated Tools Reduce LLM Token Usage and Improve AI Agent Governance”.
Key questions
Q: Why do policy-based tool sets improve AI agent governance?
A: They move authorisation to discovery time, before the model can choose from the enterprise catalog.
Q: How do security teams know whether curated tools are actually helping?
A: Look for three signals: fewer tools returned per agent, cleaner audit trails linking policy to execution, and lower variance between the tools an agent is allowed to see and the tools it actually uses.
Q: What breaks when AI agents discover tools at runtime instead of using hardcoded lists?
A: Hardcoded lists assume the tool set is stable enough to be embedded in code.
Practitioner guidance
- Define tool access by role and purpose Create named policies that map each agent to a specific business function, then allow only the tools required for that role.
- Filter tools before model discovery Return only approved tools at request time so the agent never receives the full enterprise catalog as available choices.
- Separate catalog size from authorisation scope Treat tool inventory growth as a governance issue and review whether newly added tools expand the agent’s discoverable surface unnecessarily.
Bottom line: AI agent tool curation narrows the discovery surface so an agent only sees the tools its policy allows, rather than the full enterprise catalog.
Glossary terms: AI Agent Tool Curation, Tool discovery, Policy-Based Access Control, Model Context Overhead
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Tool discovery is now an access-control decision, not just a usability choice. When a model receives only the tools its policy authorises, the governance boundary moves upstream from execution to discovery. That is a stronger identity pattern because the agent cannot select what it never sees, and the enterprise can reason about entitlement before action. The practitioner takeaway is that tool visibility should be treated as part of authorisation design, not as a UI convenience.
A few things that frame the scale:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: What is the difference between tool curation and simply hiding tools from the model?
A: Curation is an authorisation control, while hiding is only a presentation choice. If a tool is merely hidden, it may still exist in the wider environment and be recoverable through other paths or future requests. If it is filtered by policy at discovery time, it is never presented as available to that agent in the first place.
👉 Read our full editorial: Tool curation for AI agents cuts LLM context overhead