Low Risk

lookup_ens_address

Lookup the ENS name for an Ethereum address (reverse resolution)

How to control lookup_ens_address ↓

AI agents call lookup_ens_address to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This is a read-only operation that queries ENS (Ethereum Name Service) to retrieve a name associated with an address. It has no side effects, does not execute code, does not modify data, and does not involve financial transactions. The operation is a simple lookup/query, fitting the Read category with low severity due to minimal potential for misuse (returns public blockchain data).

From the tool's definition Tool performs 'Lookup' and 'reverse resolution' of ENS names - retrieves existing data without modification or execution.

Documented attack patterns abuse exactly the kind of access lookup_ens_address gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for lookup_ens_address:

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

lookup_ens_address is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register BNB Chain MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the lookup_ens_address tool do? +

Lookup the ENS name for an Ethereum address (reverse resolution). It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookup_ens_address? +

Register the BNB Chain MCP server in PolicyLayer and add a rule for lookup_ens_address: 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 BNB Chain MCP. Nothing to install.

What risk level is lookup_ens_address? +

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

Can I rate-limit lookup_ens_address? +

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

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

lookup_ens_address is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BNB Chain MCP tool call.

Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.