check_contract_before_interaction
txpeek: Check an address for risk right before you send a transaction to it, approve it, or buy its token (Base or Ethereum). For a full scan of verified source use scan_contract_address; for a token's sellability use check_token_honeypot. Returns verdict (low | caution | high | unknown), risk_sc...
This record as markdown: /tools/dev-tanod-tanod/check-contract-before-interaction.md
What check_contract_before_interaction does on Tanod
AI agents call check_contract_before_interaction 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 the contract is deployed on. |
address | string | Yes | Address you are about to interact with (0x + 40 hex). |
Parameters from the server's own tool schema.
Why check_contract_before_interaction is rated Low
Even though check_contract_before_interaction 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.
Attacks that exploit this kind of access
The rule that runs check_contract_before_interaction 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 check_contract_before_interaction, this is the rule to start with:
check_contract_before_interaction 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 check_contract_before_interaction call is checked against it from then on.
Questions about check_contract_before_interaction
txpeek: Check an address for risk right before you send a transaction to it, approve it, or buy its token (Base or Ethereum). For a full scan of verified source use scan_contract_address; for a token's sellability use check_token_honeypot. Returns verdict (low | caution | high | unknown), risk_score 0-100 and plain-language reasons, e.g. upgradeable by a single key, unverified source, mint/blacklist/fee functions, SELFDESTRUCT or DELEGATECALL, an EOA where a contract was expected. Price: USD 0.005. Free: 3 scans or 30 txpeek checks per IP per UTC day. Typically under 1 s (p95 about 1 s), at most about 4 s; results are cached for 10 min. If the chain cannot be read the call fails and is not charged. Heuristic, not an audit: the buy/sell (honeypot) simulation of ERC-20 tokens sees one trade now, there is no oracle analysis, and a low verdict is not a clearance. Docs: https://tanod.dev/learn/contract-address-risk-check-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
check_contract_before_interaction 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 check_contract_before_interaction: 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.
check_contract_before_interaction 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 check_contract_before_interaction 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 check_contract_before_interaction. 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.
check_contract_before_interaction 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