Get detailed information about a specific governance proposal including full description, votes, and execution status.
AI agents call governance_get_proposal_details 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 and queries governance proposal metadata without side effects. It does not create, modify, delete, or execute any operations; it only fetches existing information for inspection. This is a clear Read operation with minimal risk.
From the tool's definition Tool name and description indicate it 'Get[s] detailed information about a specific governance proposal including full description, votes, and execution status' — purely data retrieval with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access governance_get_proposal_details 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_proposal_details:
{
"version": "1",
"default": "deny",
"tools": {
"governance_get_proposal_details": {}
}
}governance_get_proposal_details 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 detailed information about a specific governance proposal including full description, votes, and execution status. 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_proposal_details: 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_proposal_details 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_proposal_details 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_proposal_details. 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_proposal_details 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.