Get VELAR token circulating supply
AI agents call velar_get_circulating_supply to retrieve information from Stacks AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves read-only information about token supply metrics. It has no side effects, does not execute transactions, does not modify state, and does not move funds. The blast radius of misuse is minimal—an agent could only retrieve public blockchain data that would be accessible through standard queries anyway.
From the tool's definition The tool name 'velar_get_circulating_supply' and description 'Get VELAR token circulating supply' indicate a data retrieval operation that queries blockchain state without modifying any data or triggering transactions.
Attacks that exploit this kind of access
Get VELAR token circulating supply. It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for velar_get_circulating_supply: 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 Stacks AI MCP Server. Nothing to install.
velar_get_circulating_supply 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 velar_get_circulating_supply 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 velar_get_circulating_supply. 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.
velar_get_circulating_supply is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). 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 →