Medium Risk

create_listing

List an ENS name for sale on NameWhisper's marketplace via Seaport 1.6. Returns an unsigned Seaport OrderComponents payload (plus EIP-712 domain/types) that the caller's wallet signs. After signing, POST the { orderComponents, signature, label, orderType: 'listing' } payload to https://namewhispe...

Part of the Name Whisper — ENS Intelligence Layer server.

create_listing can modify Name Whisper — ENS Intelligence Layer data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE NAME WHISPER — ENS INTELLIGENCE LAYER →

Free to start. No card required.

AI agents use create_listing to create or modify resources in Name Whisper — ENS Intelligence Layer. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call create_listing repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Name Whisper — ENS Intelligence Layer.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_listing": {
      "limits": [
        {
          "counter": "create_listing_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 create_listing 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 create_listing only ever does what you allow.

SECURE NAME WHISPER — ENS INTELLIGENCE LAYER →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the create_listing tool do? +

List an ENS name for sale on NameWhisper's marketplace via Seaport 1.6. Returns an unsigned Seaport OrderComponents payload (plus EIP-712 domain/types) that the caller's wallet signs. After signing, POST the { orderComponents, signature, label, orderType: 'listing' } payload to https://namewhisper.ai/api/orderbook/submit (authenticated) to store the order. Fee structure: 1% marketplace fee baked into the order as a Seaport consideration item (seller-paid, not added on top). NW-native only — MCP listings stay on NameWhisper. If you want your listing on OpenSea too, list it separately through their interface. Requires the wallet to have approved NameWrapper (for wrapped names) or BaseRegistrar (for unwrapped) as an operator first. Use approve_operator if needed. Tip: Use get_valuation first to price competitively. Use get_name_details to confirm the name is unwrapped vs wrapped before listing.. It is categorised as a Write tool in the Name Whisper — ENS Intelligence Layer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_listing? +

Register the Name Whisper — ENS Intelligence Layer MCP server in PolicyLayer and add a rule for create_listing: 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 create_listing? +

create_listing is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_listing? +

Yes. Add a rate_limit block to the create_listing 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 create_listing completely? +

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

create_listing 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.