Okta targets AI agent token costs with MCP scoping
AI-summarised brief · reviewed before publication
Okta introduces identity-scoped Model Context Protocol (MCP) tool lists to reduce AI agent token costs, addressing what it terms the “tool tax.” This overhead occurs when models process schemas for all exposed tools, even those unused or unauthorized. Okta’s solution filters tools before they reach the model, using permissions assigned to agent and user identities. Internal modeling indicates this approach can reduce visible tools by over 90% in certain permission scenarios, significantly lowering associated schema costs. The company distinguishes this identity-based scoping from gateway spending controls, emphasizing least-privilege access at the tool level. Administrators configure allowed tools in the Okta dashboard, ensuring agents only receive authorized tool sets in their prompts. While Okta did not provide absolute dollar figures, it asserts that token consumption tracks nearly linearly with tool count. The strategy aims to solve both tool-count and user-count problems inherent in current MCP server architectures, preventing unauthorized access attempts while optimizing prompt efficiency for enterprise AI deployments.
💡 Why It Matters
- · By shifting access control from the execution layer to the prompt construction phase, Okta tackles the hidden inefficiency of paying for unused tool definitions.
- · This approach transforms identity management into a direct cost-saving mechanism for AI operations, rather than just a security checkpoint.