Get voting power for a specific address based on their veSPA holdings.
AI agents call governance_get_voting_power 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 queries voting power data derived from veSPA token holdings. It performs no mutations, no financial transactions, no code execution, and no destructive operations. It is a pure data retrieval operation with no side effects.
From the tool's definition Tool name is 'governance_get_voting_power' and description states 'Get voting power for a specific address based on their veSPA holdings.' The verb 'Get' and phrase 'based on their veSPA holdings' indicate a read-only query operation that retrieves voting…
Documented attack patterns abuse exactly the kind of access governance_get_voting_power 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 governance_get_voting_power:
{
"version": "1",
"default": "deny",
"tools": {
"governance_get_voting_power": {}
}
}governance_get_voting_power 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 voting power for a specific address based on their veSPA holdings. 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 governance_get_voting_power: 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.
governance_get_voting_power 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 governance_get_voting_power 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 governance_get_voting_power. 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.
governance_get_voting_power 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.