WHOIS-style lookup using RDAP (Registration Data Access Protocol).
AI agents call rdap_lookup to retrieve information from Network MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
RDAP/WHOIS lookups are read-only queries against public registries. They retrieve information about IP address ownership, network allocations, and domain registration details without side effects, data modification, code execution, or destructive operations. The low severity reflects that such data is publicly accessible and misuse carries minimal blast radius.
From the tool's definition Tool performs 'WHOIS-style lookup using RDAP (Registration Data Access Protocol)' — a query operation that retrieves registration and network ownership data without modification or execution of external commands.
Attacks that exploit this kind of access
WHOIS-style lookup using RDAP (Registration Data Access Protocol). It is categorised as a Read tool in the Network MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Network MCP Server MCP server in PolicyLayer and add a rule for rdap_lookup: 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 Network MCP Server. Nothing to install.
rdap_lookup 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 rdap_lookup 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 rdap_lookup. 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.
rdap_lookup is provided by the Network MCP Server MCP server (labeveryday/network-mcp). 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 →