get_base_code
Check if a Base address is a contract and return bytecode size via eth_getCode.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/get-base-code.md
What get_base_code does on Delx Protocol — Agent Recovery & Continuity
AI agents call get_base_code to retrieve information from Delx Protocol — Agent Recovery & Continuity without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
block | string | — | |
address | string | Yes |
Parameters from the server's own tool schema.
Why get_base_code is rated Low
This is fundamentally a Read operation—it queries blockchain state without writing or executing transactions. However, severity is critical because: (1) it provides direct access to Ethereum RPC endpoints, enabling reconnaissance attacks; (2) an AI agent could use this to systematically scan addresses and enumerate contract deployments; (3) the tool's access to bytecode enables contract analysis that could precede…
From the tool's definition Tool description states 'return bytecode size via eth_getCode', which retrieves blockchain data. The name 'get_base_code' and description indicate querying/reading operations without modification.
Attacks that exploit this kind of access
The rule that runs get_base_code safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_base_code, this is the rule to start with:
get_base_code is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every get_base_code call is checked against it from then on.
Questions about get_base_code
Check if a Base address is a contract and return bytecode size via eth_getCode. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
get_base_code accepts 2 parameters: block, address. Required: address. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for get_base_code: 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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.
get_base_code 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_base_code 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_base_code. 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_base_code is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue