Resolve a .find or .fn domain to an address
AI agents call resolve_domain to retrieve information from Flow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward lookup operation, mapping a domain name to a blockchain address. It only retrieves data with no side effects, modifications, or financial implications.
From the tool's definition Resolve a .find or .fn domain to an address
Attacks that exploit this kind of access
Resolve a .find or .fn domain to an address. It is categorised as a Read tool in the Flow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Flow MCP Server MCP server in PolicyLayer and add a rule for resolve_domain: 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 Flow MCP Server. Nothing to install.
resolve_domain 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_domain 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_domain. 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_domain is provided by the Flow MCP Server MCP server (lmcmz/flow-mcp-server). 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 →