get_contract_info
Get metadata about a verified smart contract: name, compiler, classification, supported adapters, and counts of functions and events. Accepts either a curated slug (uni-eth, usdc-base, …) or chain+address.
This record as markdown: /tools/defi-io-smartcontract/get-contract-info.md
What get_contract_info does on Smarts Md
AI agents call get_contract_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 'uni-eth' or 'univ3-usdc-weth-eth'. Alternative to chain+address. |
chain | string | — | Chain slug: eth, base, arbitrum, optimism, or polygon. Required unless `slug` is given. |
address | string | — | The 0x-prefixed EVM contract address. Required unless `slug` is given. |
Parameters from the server's own tool schema.
Why get_contract_info is rated Low
This tool performs read-only queries against a smart contract information database. It returns static metadata about deployed contracts without any side effects, state changes, or code execution. The blast radius of misuse is minimal—an attacker could only retrieve publicly available contract information, which poses no direct risk to systems or users.
From the tool's definition Tool retrieves metadata about smart contracts: name, compiler, classification, supported adapters, and counts of functions and events. Description explicitly indicates data retrieval ("Get metadata") with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_contract_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_contract_info, this is the rule to start with:
get_contract_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_contract_info call is checked against it from then on.
Questions about get_contract_info
Get metadata about a verified smart contract: name, compiler, classification, supported adapters, and counts of functions and events. Accepts either a curated slug (uni-eth, usdc-base, …) 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_contract_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_contract_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_contract_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_contract_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_contract_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_contract_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