AI agents call resolve_name to retrieve information from UluVoiMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a name resolution query (similar to DNS lookup), retrieving blockchain address information from a name. It has no side effects, does not modify data, and is purely a read/fetch operation. Severity is low as misuse would only expose address mappings.
From the tool's definition Resolve an enVoi name — resolves a name to an address/identity, a read-only lookup operation
Attacks that exploit this kind of access
Resolve an enVoi name (e.g. It is categorised as a Read tool in the UluVoiMCP MCP Server, which means it retrieves data without modifying state.
Register the UluVoi MCP server in PolicyLayer and add a rule for resolve_name: 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 UluVoiMCP. Nothing to install.
resolve_name 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 resolve_name 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 resolve_name. 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.
resolve_name is provided by the UluVoi MCP server (maidtoshelly/uluvoimcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →