detect_proxy
chainpeek: detect whether a contract is a proxy, and of which kind. For code size and hash use get_contract_code. Reads the code, the EIP-1967 / EIP-1822 / OpenZeppelin legacy slots and slot 0, then one multicall. Returns is_contract, is_proxy, kind (eip1967_transparent | eip1967_uups | eip1967 |...
This record as markdown: /tools/dev-tanod-tanod/detect-proxy.md
What detect_proxy does on Tanod
AI agents call detect_proxy to retrieve information from Tanod 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 |
|---|---|---|---|
chain | string | Yes | Chain to read. |
address | string | Yes | Contract address (0x + 40 hex). |
Parameters from the server's own tool schema.
Why detect_proxy is rated Low
Even though detect_proxy only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs detect_proxy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For detect_proxy, this is the rule to start with:
detect_proxy 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 Tanod, apply this rule, and every detect_proxy call is checked against it from then on.
Questions about detect_proxy
chainpeek: detect whether a contract is a proxy, and of which kind. For code size and hash use get_contract_code. Reads the code, the EIP-1967 / EIP-1822 / OpenZeppelin legacy slots and slot 0, then one multicall. Returns is_contract, is_proxy, kind (eip1967_transparent | eip1967_uups | eip1967 | eip1967_beacon | eip1822_uups | oz_legacy | eip1167_minimal | erc7511_minimal | eip7702_delegation, or the multisig-wallet kind when slot 0 and masterCopy() agree), implementation (and whether it has code), admin, beacon and the raw slots. An upgradeable proxy's implementation can change after this read. A malformed or inconsistent node answer is a 5xx and is not charged. Typically 1-4 s. Price: USD 0.002. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/proxy-contract-detection-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
detect_proxy accepts 2 parameters: chain, address. Required: chain, address. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for detect_proxy: 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 Tanod. Nothing to install.
detect_proxy 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 detect_proxy 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 detect_proxy. 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.
detect_proxy is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue