Get real-time circulating supply for SPA and USDs tokens. Circulating supply excludes locked tokens, treasury holdings, and burned tokens.
AI agents call supply_get_circulating to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple data retrieval operation that queries token supply information. It has no side effects, cannot modify state, and poses minimal risk if invoked by an AI agent. It falls squarely within the Read category.
From the tool's definition Tool name and description indicate data retrieval only: 'Get real-time circulating supply' with no modification, deletion, or execution capabilities. Returns token supply metrics as a query operation.
Documented attack patterns abuse exactly the kind of access supply_get_circulating gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for supply_get_circulating:
{
"version": "1",
"default": "deny",
"tools": {
"supply_get_circulating": {}
}
}supply_get_circulating is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get real-time circulating supply for SPA and USDs tokens. Circulating supply excludes locked tokens, treasury holdings, and burned tokens. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain MCP server in PolicyLayer and add a rule for supply_get_circulating: 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 BNB Chain MCP. Nothing to install.
supply_get_circulating 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 supply_get_circulating 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 supply_get_circulating. 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.
supply_get_circulating is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.