Get token budget status for the current session.
AI agents call cortex_get_token_budget to retrieve information from Cortex MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about token budget for the active session. It performs no side effects, creates no data, executes no code, and causes no destructive or financial operations. It is purely informational/observational, fitting the 'Read' category with low severity as misuse would only expose metadata about session resources.
From the tool's definition Tool name 'cortex_get_token_budget' and description 'Get token budget status for the current session' indicate a retrieval operation that queries current state without modifying data.
Attacks that exploit this kind of access
Get token budget status for the current session. It is categorised as a Read tool in the Cortex MCP MCP Server, which means it retrieves data without modifying state.
Register the Cortex MCP server in PolicyLayer and add a rule for cortex_get_token_budget: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Cortex MCP. Nothing to install.
cortex_get_token_budget is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cortex_get_token_budget rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for cortex_get_token_budget. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
cortex_get_token_budget is provided by the Cortex MCP server (neuralnexustech/cortex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →