rdap_ip
Ownership record for an IP address or block via RDAP: the network name, owning organization, ASN, CIDR range, and country. Pairs with ip_reputation and entity lookups. Keyless.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/rdap-ip.md
What rdap_ip does on Livedatalink
AI agents call rdap_ip to retrieve information from Livedatalink 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 |
|---|---|---|---|
ip | string | Yes | IPv4 or IPv6 address, e.g. '8.8.8.8'. |
Parameters from the server's own tool schema.
Why rdap_ip is rated Low
This tool performs read-only lookups of publicly available RDAP (Registration Data Access Protocol) data. It retrieves and returns information about IP address ownership without modifying, deleting, executing code, or incurring financial obligations. The 'Pairs with ip_reputation and entity lookups' context further confirms it is a data retrieval tool.
From the tool's definition Tool retrieves ownership record data for IP addresses via RDAP protocol, returning network name, owning organization, ASN, CIDR range, and country. Description indicates query/lookup functionality with 'no side effects' characteristic.
Attacks that exploit this kind of access
The rule that runs rdap_ip safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rdap_ip, this is the rule to start with:
rdap_ip 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 Livedatalink, apply this rule, and every rdap_ip call is checked against it from then on.
Questions about rdap_ip
Ownership record for an IP address or block via RDAP: the network name, owning organization, ASN, CIDR range, and country. Pairs with ip_reputation and entity lookups. Keyless. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
rdap_ip accepts 1 parameter: ip. Required: ip. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for rdap_ip: 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 Livedatalink. Nothing to install.
rdap_ip 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_ip 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_ip. 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_ip is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue