inspect_address
Inspect any EVM address: classifies it as an EOA / unverified contract / EIP-7702 delegated wallet, returns native-token balance, outgoing tx count (nonce), and reverse-ENS name (Ethereum only). Works for unindexed addresses — useful before deciding whether to call get_contract_info or get_erc20_...
This record as markdown: /tools/defi-io-smartcontract/inspect-address.md
What inspect_address does on Smarts Md
AI agents call inspect_address to retrieve information from Smarts Md 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 | — | Chain slug: eth, base, arbitrum, optimism, or polygon. |
address | string | — | Any 0x-prefixed EVM address (contract or EOA). |
Parameters from the server's own tool schema.
Why inspect_address is rated Low
inspect_address performs information retrieval only. It queries blockchain state to classify addresses and fetch read-only properties (balance, transaction count, ENS records). No writes, deletions, code execution, or financial transactions occur. Blast radius is minimal—an AI misusing this tool can only gather public blockchain data that is already world-readable.
From the tool's definition The tool returns metadata about EVM addresses (classification, balance, nonce, reverse-ENS name) with no modify or destroy operations. Description confirms it retrieves data for decision-making without side effects.
Attacks that exploit this kind of access
The rule that runs inspect_address safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Smarts Md, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For inspect_address, this is the rule to start with:
inspect_address 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 Smarts Md, apply this rule, and every inspect_address call is checked against it from then on.
Questions about inspect_address
Inspect any EVM address: classifies it as an EOA / unverified contract / EIP-7702 delegated wallet, returns native-token balance, outgoing tx count (nonce), and reverse-ENS name (Ethereum only). Works for unindexed addresses — useful before deciding whether to call get_contract_info or get_erc20_info. It is categorised as a Read tool in the Smarts Md MCP Server, which means it retrieves data without modifying state.
inspect_address accepts 2 parameters: chain, address. The full parameter table on this page comes from the server's own tool schema.
Register the Smarts Md MCP server in PolicyLayer and add a rule for inspect_address: 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 Smarts Md. Nothing to install.
inspect_address 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 inspect_address 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 inspect_address. 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.
inspect_address is provided by the Smarts Md MCP server (defi-io/smartcontract). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Smarts Md, and thousands of servers like it.
This server
Across the catalogue