Get the deployed bytecode of a contract. Returns empty if address is an EOA.
AI agents call get_contract_bytecode 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 performs a data retrieval operation querying blockchain state to fetch the bytecode of a deployed contract. There are no state-changing operations, code execution, or destructive actions. Obtaining bytecode is informational and read-only, carrying minimal risk even if misused by an agent.
From the tool's definition Tool name is 'get_contract_bytecode' and description states 'Get the deployed bytecode of a contract' — this is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_contract_bytecode 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_contract_bytecode:
{
"version": "1",
"default": "deny",
"tools": {
"get_contract_bytecode": {}
}
}get_contract_bytecode 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 the deployed bytecode of a contract. Returns empty if address is an EOA. 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_contract_bytecode: 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_contract_bytecode 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_contract_bytecode 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_contract_bytecode. 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_contract_bytecode 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.