AI agents invoke execute_proposal to trigger actions in BNB Chain MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes proposals in a blockchain governance context, making it an Execute category risk. Although timelock delays provide a mitigation window, the tool itself performs irreversible state changes on-chain (deploying code, transferring assets, changing parameters) determined by proposal arguments.
From the tool's definition The tool description explicitly states "Execute a queued proposal after timelock delay," which indicates it triggers execution of a governance proposal.
Documented attack patterns abuse exactly the kind of access execute_proposal 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 execute_proposal:
{
"version": "1",
"default": "deny",
"tools": {
"execute_proposal": {
"limits": [
{
"counter": "execute_proposal_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_proposal stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute a queued proposal after timelock delay. It is categorised as a Execute tool in the BNB Chain MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the BNB Chain MCP server in PolicyLayer and add a rule for execute_proposal: 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.
execute_proposal is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_proposal 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 execute_proposal. 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.
execute_proposal 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.