Resolve a contract's interface from chain + address via a fallback ladder (Etherscan → Sourcify → proxy → heimdall decompile → 4byte). Returns a capability manifest (read vs write functions, the 'buttons'), proxy chain, token metadata, and PROVENANCE. ALWAYS read provenance: a decompiled ABI has ...
AI agents call resolve_abi to retrieve information from Gulltoppr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
chain | string | Yes | Chain alias ("ethereum", "base", "optimism", "arbitrum", "polygon", "local") or numeric chain id. |
address | string | Yes | 0x contract address. |
rpc_url | string | — | Override RPC URL. Required for chains with no default (e.g. local/31337). |
Parameters from the server's own tool schema.
This tool only retrieves and returns contract ABI/interface information from various sources. It performs read-only lookups with no side effects, no data modification, no execution of contract code, and no financial operations. The note about treating decompiled ABIs with care refers to downstream usage, not this tool's own actions.
From the tool's definition Resolve a contract's interface from chain + address via a fallback ladder (Etherscan → Sourcify → proxy → heimdall decompile → 4byte). Returns a capability manifest... proxy chain, token metadata, and PROVENANCE.
Attacks that exploit this kind of access
Resolve a contract's interface from chain + address via a fallback ladder (Etherscan → Sourcify → proxy → heimdall decompile → 4byte). Returns a capability manifest (read vs write functions, the 'buttons'), proxy chain, token metadata, and PROVENANCE. ALWAYS read provenance: a decompiled ABI has synthetic function names — treat it with care and confirm intent before writing. It is categorised as a Read tool in the Gulltoppr MCP Server, which means it retrieves data without modifying state.
resolve_abi accepts 3 parameters: chain, address, rpc_url. Required: chain, address. The full parameter table on this page comes from the server's own tool schema.
Register the Gulltoppr MCP server in PolicyLayer and add a rule for resolve_abi: 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 Gulltoppr. Nothing to install.
resolve_abi 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 resolve_abi 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 resolve_abi. 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.
resolve_abi is provided by the Gulltoppr MCP server (https://mcp.gulltoppr.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →