Low Risk

reverse_resolve_address

Get the ENS name for an Ethereum address (reverse lookup)

How to control reverse_resolve_address ↓

AI agents call reverse_resolve_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 tool performs a read-only reverse DNS-style lookup, retrieving the ENS name associated with an Ethereum address. It has no side effects, modifies no data, and simply queries on-chain ENS records.

From the tool's definition Get the ENS name for an Ethereum address (reverse lookup)

Documented attack patterns abuse exactly the kind of access reverse_resolve_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 reverse_resolve_address:

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

reverse_resolve_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 reverse_resolve_address tool do? +

Get the ENS name for an Ethereum address (reverse lookup). 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 reverse_resolve_address? +

Register the BNB Chain MCP server in PolicyLayer and add a rule for reverse_resolve_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 reverse_resolve_address? +

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

Can I rate-limit reverse_resolve_address? +

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

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

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