Low Risk

wash_check

Check if an ENS sale is a wash trade. Provide either a tx_hash to look up a pre-computed score, or provide label + buyer + seller + price_eth for live on-demand analysis. Returns a wash confidence score (0-1), a label (clean/suspicious/likely_wash), detected signals, and a human-readable summary.

Part of the Name Whisper MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call wash_check to retrieve information from Name Whisper without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though wash_check only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

namewhisper-ens-tools.yaml
tools:
  wash_check:
    rules:
      - action: allow

See the full Name Whisper policy for all 34 tools.

Tool Name wash_check
Category Read
Risk Level Low

View all 34 tools →

Agents calling read-class tools like wash_check have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the wash_check tool do? +

Check if an ENS sale is a wash trade. Provide either a tx_hash to look up a pre-computed score, or provide label + buyer + seller + price_eth for live on-demand analysis. Returns a wash confidence score (0-1), a label (clean/suspicious/likely_wash), detected signals, and a human-readable summary.. It is categorised as a Read tool in the Name Whisper MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wash_check? +

Add a rule in your Intercept YAML policy under the tools section for wash_check. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Name Whisper MCP server.

What risk level is wash_check? +

wash_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wash_check? +

Yes. Add a rate_limit block to the wash_check rule in your Intercept 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.

How do I block wash_check completely? +

Set action: deny in the Intercept policy for wash_check. 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.

What MCP server provides wash_check? +

wash_check is provided by the Name Whisper MCP server (namewhisper/ens-tools). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Name Whisper

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.