Okta targets AI agent token costs with MCP scoping

Okta says identity-scoped Model Context Protocol (MCP) software lists can scale back AI agent token costs.

Each mannequin name made by an AI agent can embody schemas, names, descriptions and parameters for each software uncovered by a MCP server. Okta calls the ensuing immediate overhead the “software tax”: tokens consumed as a mannequin considers instruments, together with these it’ll by no means name.

The firm argues that this value seems earlier than an agent makes an attempt a software name. A later rejection of an unauthorised request subsequently can not get well immediate tokens already consumed. Okta’s proposed management filters the checklist of instruments earlier than it reaches the mannequin, utilizing permissions assigned to an agent id and the consumer related with it.

Okta’s inner modelling discovered that some permission eventualities decreased the variety of seen instruments by greater than 90%. The firm stated tool-schema costs fell by roughly the identical proportion, though it didn’t present absolute token or greenback figures.

MCP software schemas create immediate overhead on each flip

MCP servers have develop into a route for connecting AI brokers to instruments and knowledge. Okta cites connections to Google Workspace, Slack and inner MCP servers as examples. An MCP server can expose numerous instruments, and the mannequin receives a illustration of every accessible software in its immediate on each flip.

That illustration features a schema. It additionally contains the software title, description and parameters.

Okta says the fee compounds when a extensively used MCP server exposes many instruments. Each energetic consumer incurs the immediate overhead at any time when their agent makes a mannequin name. The firm frames this as each a tool-count downside and a user-count downside.

The concern additionally has an access-control dimension. An agent that sees instruments exterior its authorisation scope can try to make use of them. A management that rejects the decision at runtime can block execution, although the mannequin has already obtained the software definition and used tokens to course of it.

Okta filters instruments earlier than the agent immediate is constructed

Okta positions the potential inside its “blueprint for the safe agentic enterprise”, which asks organisations to determine their brokers, their permitted connections and their authorised actions.

Its strategy narrows the connection query from entry to a complete MCP server to entry to particular person instruments on that server. An administrator configures the instruments {that a} explicit id might use within the Okta dashboard. Okta then returns the scoped software set as an alternative of the server’s full catalogue.

The agent receives this shorter checklist in its immediate for every flip. Okta says it checks scope once more at runtime earlier than a software name executes.

This design applies least-privilege entry on the software degree. The firm says an agent shouldn’t be conscious of sources, databases or instruments that it has not been expressly authorised to make use of. Removing unavailable instruments from the immediate additionally removes their schema value from the mannequin name.

Okta doesn’t describe a dwell buyer deployment within the publish. Its proof for the claimed discount comes from inner modelling utilizing Okta product knowledge and public vendor documentation, with no buyer knowledge used.

Internal mannequin used OAuth scopes and consultant roles

Okta modelled a single MCP shopper with entry to a listing of enterprise instruments. It in contrast the variety of instruments seen to the mannequin earlier than and after identity-based scoping.

To estimate scoped publicity, the corporate mapped Okta MCP Server instruments to the OAuth scopes that unlock them. It then outlined consultant consumer segments. These included helpdesk read-only customers and helpdesk operators.

Other segments had been app directors, model and e-mail directors, and tremendous directors. Okta weighted every section in accordance with an assumed share of month-to-month site visitors.

The firm calculated tool-count discount as one minus the ratio of scoped instruments to unscoped instruments. It stated some eventualities eliminated greater than 90% of seen instruments. Its publish states that tool-schema token value tracks software depend practically linearly as a result of every software contributes its title, description and parameter schema to each immediate.

Okta says precise outcomes fluctuate in accordance with the software catalogue, distribution of permissions and mannequin chosen. Average schema measurement, request quantity and mannequin pricing additionally have an effect on absolute token and greenback costs.

Okta contrasts id entitlements with gateway spending controls

The publish distinguishes identity-based scoping from gateway controls. Okta says gateways can cap spending by key, staff or group, and might help routing and charge limiting.

A gateway can meter tokens coming into and leaving a system, in addition to {dollars} spent. Okta says these controls can restrict costs after a mannequin determination turns into costly.

Identity entitlements present a unique enter. Okta says per-user and per-agent entitlements can decide the instruments accessible to a particular agent or the particular person behind that agent, fairly than making use of entry data at group degree.

Paul Webber, Principal Cybersecurity Industry Analyst at Software Analyst Cyber Research, stated: “Cost management for brokers is finest supplied utilizing id governance instruments that provide extra granular management and precision with out disrupting enterprise processes.

“Okta’s strategy is a chic approach to do that as a result of it leverages the identical entitlement knowledge that governs safety, not a separate metering layer with out that perception.”

Okta’s account presents the gateway as a management for what passes by it. The id layer filters the accessible software set earlier than these instruments have to be metered.

Tool visibility additionally impacts MCP assault publicity

The publish ties the identical mechanism to safety publicity. Okta says eradicating instruments from an unauthorised id’s view additionally removes actions that id might take if it had been compromised.

Its proposed scope test operates at two factors. The first happens because the software checklist is assembled for the agent immediate. The second happens when the agent makes an attempt to execute a software name.

Okta describes the outcome as a smaller blast radius for a compromised id. The remaining uncovered instruments decide the set of actions accessible to that id. In the corporate’s mannequin, the immediate comprises solely instruments related with the id’s authorised OAuth scopes.

For organisations assessing MCP entry, software stock and entitlement mapping are the principle operational inputs. Okta’s methodology maps MCP Server instruments to the OAuth scopes that unlock them, then compares the complete software catalogue with the scoped catalogue seen to every consultant consumer section.

Okta is a key sponsor of this 12 months’s AI & Big Data Expo Europe held in Amsterdam on 19-20 October 2026.

See additionally: Meta Muse Glimmer brings local AI agents to consumer GPUs

Want to be taught extra about AI and large knowledge from trade leaders? Check out AI & Big Data Expo happening in Amsterdam, California, and London. The complete occasion is a part of TechEx and is co-located with different main know-how occasions together with the Cyber Security & Cloud Expo. Click here for extra data.

AI News is powered by TechForge Media. Explore different upcoming enterprise know-how occasions and webinars here.

The publish Okta targets AI agent token costs with MCP scoping appeared first on AI News.