reverse_resolve_ens
Reverse-resolve an Ethereum address to its primary ENS name. Returns null if no primary name is set.
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/reverse-resolve-ens.md
What reverse_resolve_ens does on VaultPilot MCP
AI agents call reverse_resolve_ens to retrieve information from VaultPilot MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
address | object | Yes |
Parameters from the server's own tool schema.
Why reverse_resolve_ens is rated Low
This tool only performs a lookup/query operation — it resolves an Ethereum address to an ENS name. There are no side effects, no data modification, no financial transactions, and no execution of commands. It is a pure read operation with minimal blast radius if misused.
From the tool's definition Reverse-resolve an Ethereum address to its primary ENS name. Returns null if no primary name is set.
Attacks that exploit this kind of access
The rule that runs reverse_resolve_ens safely
PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reverse_resolve_ens, this is the rule to start with:
reverse_resolve_ens is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every reverse_resolve_ens call is checked against it from then on.
Questions about reverse_resolve_ens
Reverse-resolve an Ethereum address to its primary ENS name. Returns null if no primary name is set. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
reverse_resolve_ens accepts 1 parameter: address. Required: address. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for reverse_resolve_ens: 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 VaultPilot MCP. Nothing to install.
reverse_resolve_ens is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the reverse_resolve_ens 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.
Set action: deny in the PolicyLayer policy for reverse_resolve_ens. 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.
reverse_resolve_ens is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on VaultPilot, and thousands of servers like it.
This server
Across the catalogue