rdap_domain
Registration record for a domain via RDAP (the modern WHOIS): registrar, creation/update/expiration dates, status flags, nameservers, and DNSSEC. Useful for due diligence and OSINT on a company's web presence. Keyless.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/rdap-domain.md
What rdap_domain does on Livedatalink
AI agents use rdap_domain to create or update resources in Livedatalink, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livedatalink environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name, e.g. 'example.com'. |
Parameters from the server's own tool schema.
Why rdap_domain is rated Medium
An AI agent can call rdap_domain faster than any human can review: one bad instruction and it creates or modifies resources in Livedatalink by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs rdap_domain 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_domain, this is the rule to start with:
rdap_domain stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_domain call is checked against it from then on.
Questions about rdap_domain
Registration record for a domain via RDAP (the modern WHOIS): registrar, creation/update/expiration dates, status flags, nameservers, and DNSSEC. Useful for due diligence and OSINT on a company's web presence. Keyless. It is categorised as a Write tool in the Livedatalink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
rdap_domain accepts 1 parameter: domain. Required: domain. 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_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 Livedatalink. Nothing to install.
rdap_domain is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rdap_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 rdap_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.
rdap_domain 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