get_erc20_info
Get live state of an ERC-20 token: supply (raw + human-formatted), price, market cap, issuer, plus centralized-stablecoin admin controls (paused status, owner / masterMinter / pauser / blacklister / rescuer) when the contract exposes them. Accepts slug or chain+address.
This record as markdown: /tools/defi-io-smartcontract/get-erc20-info.md
What get_erc20_info does on Smarts Md
AI agents call get_erc20_info 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 |
|---|---|---|---|
slug | string | — | Curated slug like 'usdc-eth' or 'usdc-base'. Alternative to chain+address. |
chain | string | — | Chain slug: eth, base, arbitrum, optimism, or polygon. Required unless `slug` is given. |
address | string | — | Token address (0x-prefixed). Required unless `slug` is given. |
Parameters from the server's own tool schema.
Why get_erc20_info is rated Low
This tool queries immutable and mutable state data from blockchain contracts (supply, price, admin controls) but performs no writes, deletions, or code execution. The exposure of admin control information (paused status, owner addresses) is informational only; reading these values poses no direct harm.
From the tool's definition "Get live state of an ERC-20 token: supply, price, market cap, issuer" and "accepts slug or chain+address" — this retrieves contract state without modifying it. No creation, deletion, or execution of external operations occurs.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_erc20_info 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 get_erc20_info, this is the rule to start with:
get_erc20_info 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 get_erc20_info call is checked against it from then on.
Questions about get_erc20_info
Get live state of an ERC-20 token: supply (raw + human-formatted), price, market cap, issuer, plus centralized-stablecoin admin controls (paused status, owner / masterMinter / pauser / blacklister / rescuer) when the contract exposes them. Accepts slug or chain+address. It is categorised as a Read tool in the Smarts Md MCP Server, which means it retrieves data without modifying state.
get_erc20_info accepts 3 parameters: slug, 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 get_erc20_info: 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.
get_erc20_info 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_erc20_info 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_erc20_info. 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_erc20_info 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