Low Risk

make_offer

Place an offer (bid) on a registered ENS name on NameWhisper via Seaport 1.6. Returns an unsigned Seaport OrderComponents payload (plus EIP-712 domain/types) that the caller's wallet signs. The buyer offers WETH and receives the name on acceptance. After signing, POST { orderComponents, signature...

Part of the Name Whisper — ENS Intelligence Layer server.

make_offer is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE NAME WHISPER — ENS INTELLIGENCE LAYER →

Free to start. No card required.

AI agents call make_offer to retrieve information from Name Whisper — ENS Intelligence Layer 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 make_offer 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "make_offer": {}
  }
}

See the full Name Whisper — ENS Intelligence Layer policy for all 42 tools.

Get this rule live on your own Name Whisper — ENS Intelligence Layer server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NAME WHISPER — ENS INTELLIGENCE LAYER →

View all 42 tools →

These attack patterns abuse exactly the kind of access make_offer gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so make_offer only ever does what you allow.

SECURE NAME WHISPER — ENS INTELLIGENCE LAYER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the make_offer tool do? +

Place an offer (bid) on a registered ENS name on NameWhisper via Seaport 1.6. Returns an unsigned Seaport OrderComponents payload (plus EIP-712 domain/types) that the caller's wallet signs. The buyer offers WETH and receives the name on acceptance. After signing, POST { orderComponents, signature, label, orderType: 'offer', variant: 'nw' } to https://namewhisper.ai/api/orderbook/submit (authenticated) to store the offer in NameWhisper's orderbook — the owner sees it and can accept, counter, or decline. Offers settle in WETH: the maker needs wrapped ETH and an approval for Seaport to spend it (the NameWhisper UI handles this approval automatically at signing time). Fee structure: 1% marketplace fee baked into the order as a Seaport consideration item. NW-native only — offers are not cross-posted to other marketplaces. Tip: Use get_valuation first to understand fair market value before making an offer.. It is categorised as a Read tool in the Name Whisper — ENS Intelligence Layer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on make_offer? +

Register the Name Whisper — ENS Intelligence Layer MCP server in PolicyLayer and add a rule for make_offer: 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 Name Whisper — ENS Intelligence Layer. Nothing to install.

What risk level is make_offer? +

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

Can I rate-limit make_offer? +

Yes. Add a rate_limit block to the make_offer 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.

How do I block make_offer completely? +

Set action: deny in the PolicyLayer policy for make_offer. 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 make_offer? +

make_offer is provided by the Name Whisper — ENS Intelligence Layer MCP server (https://namewhisper.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Name Whisper — ENS Intelligence Layer tool call.

Deterministic rules across all 42 Name Whisper — ENS Intelligence Layer tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.