util_rdap_lookup
Fetch registrar, status, and registration dates for trust, compliance, and domain ops.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-rdap-lookup.md
What util_rdap_lookup does on Delx Mcp A2a
AI agents call util_rdap_lookup to retrieve information from Delx Mcp A2a 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 |
|---|---|---|---|
domain | string | Yes | Domain to inspect |
timeout | integer | — | Timeout in seconds (1-15) |
Parameters from the server's own tool schema.
Why util_rdap_lookup is rated Low
util_rdap_lookup performs RDAP (Registration Data Access Protocol) queries to retrieve domain registration metadata (registrar, status, dates). This is a pure data retrieval operation with no side effects, no code execution, and no capability to modify or delete data. The terms 'Fetch' and 'lookup' confirm read-only semantics.
From the tool's definition Tool name includes 'lookup' and description states 'Fetch registrar, status, and registration dates' — all read operations with no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs util_rdap_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_rdap_lookup, this is the rule to start with:
util_rdap_lookup 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 Delx Mcp A2a, apply this rule, and every util_rdap_lookup call is checked against it from then on.
Questions about util_rdap_lookup
Fetch registrar, status, and registration dates for trust, compliance, and domain ops. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
util_rdap_lookup accepts 2 parameters: domain, timeout. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_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 Delx Mcp A2a. Nothing to install.
util_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 util_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 util_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.
util_rdap_lookup is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue