meta-tools.token_balance
Get the current API token balance for the authenticated account. Returns tokens used, tokens remaining, monthly allowance, billing plan, and when the allowance resets (billing_period_end). Use this before expensive calls or when you receive a 402 insufficient_tokens response Cost = 0 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/meta-tools.token-balance.md
What meta-tools.token_balance does on Vee3
AI agents call meta-tools.token_balance to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why meta-tools.token_balance is rated Low
This tool only retrieves and reports the state of the authenticated account's token usage and billing information. It is a read-only query with no side effects, no code execution, and no data modification. The severity is low because misuse by an AI agent would only expose account status information already available to the authenticated user, with no destructive or financial consequences from reading this data.
From the tool's definition Tool description explicitly states it "Get[s] the current API token balance" and returns account metadata (tokens_used, tokens_remaining, monthly_allowance, billing_plan, billing_period_end).
Attacks that exploit this kind of access
The rule that runs meta-tools.token_balance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For meta-tools.token_balance, this is the rule to start with:
meta-tools.token_balance is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every meta-tools.token_balance call is checked against it from then on.
Questions about meta-tools.token_balance
Get the current API token balance for the authenticated account. Returns tokens used, tokens remaining, monthly allowance, billing plan, and when the allowance resets (billing_period_end). Use this before expensive calls or when you receive a 402 insufficient_tokens response Cost = 0 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
Register the Vee3 MCP server in PolicyLayer and add a rule for meta-tools.token_balance: 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 Vee3. Nothing to install.
meta-tools.token_balance 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 meta-tools.token_balance 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 meta-tools.token_balance. 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.
meta-tools.token_balance is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue