Get user statistics for the Sperax protocol including holder counts, distribution, and activity metrics.
AI agents call analytics_get_user_stats 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 tool performs information querying about the Sperax protocol without side effects. It falls squarely under the Read category as it accesses and returns statistical data. The severity is low because unauthorized access to aggregate user statistics poses minimal direct harm — such metrics are often publicly available and do not grant control over financial operations or data modification.
From the tool's definition Tool retrieves 'user statistics', 'holder counts', 'distribution', and 'activity metrics' — all read-only data retrieval operations with no capability to modify, delete, or execute code.
Documented attack patterns abuse exactly the kind of access analytics_get_user_stats 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 analytics_get_user_stats:
{
"version": "1",
"default": "deny",
"tools": {
"analytics_get_user_stats": {}
}
}analytics_get_user_stats 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 user statistics for the Sperax protocol including holder counts, distribution, and activity metrics. 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 analytics_get_user_stats: 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.
analytics_get_user_stats 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 analytics_get_user_stats 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 analytics_get_user_stats. 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.
analytics_get_user_stats 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.