# 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.

Agent View of the PolicyLayer registry record for `inspect_address`. HTML page: https://policylayer.com/tools/defi-io-smartcontract/inspect-address

## Facts

- Tool: `inspect_address`
- Server: Smarts Md (`defi-io/smartcontract`) — https://policylayer.com/tools/defi-io-smartcontract.md
- Homepage: https://github.com/defi-io/smartcontract
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 2
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `chain` | string | no | Chain slug: eth, base, arbitrum, optimism, or polygon. |
| `address` | string | no | Any 0x-prefixed EVM address (contract or EOA). |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "inspect_address",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Smarts Md:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "inspect_address": {}
  }
}
```

## Other tools on Smarts Md (4)

- `get_contract_info` — Read — https://policylayer.com/tools/defi-io-smartcontract/get-contract-info.md
- `get_erc20_info` — Read — https://policylayer.com/tools/defi-io-smartcontract/get-erc20-info.md
- `get_uniswap_v3_pool` — Read — https://policylayer.com/tools/defi-io-smartcontract/get-uniswap-v3-pool.md
- `read_contract_state` — Read — https://policylayer.com/tools/defi-io-smartcontract/read-contract-state.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=defi-io-smartcontract · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/defi-io-smartcontract