Low Risk

subgraph_protocol_stats

Get aggregated protocol statistics from all subgraphs. Overview of TVL, holders, and activity.

How to control subgraph_protocol_stats ↓

AI agents call subgraph_protocol_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.

Low Risk

This tool retrieves and queries existing protocol data (TVL, holders, activity metrics) from subgraphs without creating, modifying, deleting, or executing operations. It is a pure read operation with no side effects, fitting the 'Read' category. The low severity reflects that querying public statistics poses minimal risk if misused by an AI agent.

From the tool's definition Tool description states 'Get aggregated protocol statistics from all subgraphs. Overview of TVL, holders, and activity.' The verb 'Get' and the read-only nature of retrieving aggregated statistics indicate no data modification, deletion, or execution of…

Documented attack patterns abuse exactly the kind of access subgraph_protocol_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 subgraph_protocol_stats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "subgraph_protocol_stats": {}
  }
}

subgraph_protocol_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register BNB Chain MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the subgraph_protocol_stats tool do? +

Get aggregated protocol statistics from all subgraphs. Overview of TVL, holders, and activity. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on subgraph_protocol_stats? +

Register the BNB Chain MCP server in PolicyLayer and add a rule for subgraph_protocol_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.

What risk level is subgraph_protocol_stats? +

subgraph_protocol_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit subgraph_protocol_stats? +

Yes. Add a rate_limit block to the subgraph_protocol_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.

How do I block subgraph_protocol_stats completely? +

Set action: deny in the PolicyLayer policy for subgraph_protocol_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.

What MCP server provides subgraph_protocol_stats? +

subgraph_protocol_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.

Enforce policy on every BNB Chain MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.