Get current token usage status and model information
AI agents call get_token_status to retrieve information from OpenAI Token Manager MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports current state information (token usage, model metadata) with no side effects. It does not create, modify, delete, or execute operations. The read-only nature—fetching status for informational purposes—places it firmly in the Read category with low risk.
From the tool's definition Tool name 'get_token_status' and description 'Get current token usage status and model information' indicate a retrieval-only operation that queries usage metrics and configuration without modifying data or executing external operations.
Attacks that exploit this kind of access
Get current token usage status and model information. It is categorised as a Read tool in the OpenAI Token Manager MCP MCP Server, which means it retrieves data without modifying state.
Register the OpenAI Token Manager MCP server in PolicyLayer and add a rule for get_token_status: 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 OpenAI Token Manager MCP. Nothing to install.
get_token_status 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 get_token_status 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 get_token_status. 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.
get_token_status is provided by the OpenAI Token Manager MCP server (opaldecisionsciences/openai-token-manager-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 →