Get voting power for an address at a specific block
AI agents call 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 retrieves/queries voting power data associated with a blockchain address at a historical block state. It performs no side effects—no data is created, modified, deleted, or financial operations executed. The action is purely informational and read-only, fitting squarely into the Read category.
From the tool's definition Tool name 'get_voting_power' and description 'Get voting power for an address at a specific block' indicate a query operation that retrieves governance voting power information. No state modification, execution of code, or financial transactions occur.
Documented attack patterns abuse exactly the kind of access 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 get_voting_power:
{
"version": "1",
"default": "deny",
"tools": {
"get_voting_power": {}
}
}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 an address at a specific block. 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 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.
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 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 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.
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.