reverse_dns

Resolve the PTR (reverse DNS) records for an IP address — the hostname(s) the IP maps back to. Args: - ip (string): IPv4 or IPv6 address. - response_format (

Server Domain Security ortamarco/domain-security-mcp-server
Category Read
Risk class Low
Parameters 00 required

What reverse_dns does on Domain Security

AI agents call reverse_dns to retrieve information from Domain Security without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why reverse_dns needs a policy

Reverse DNS (PTR) lookups are standard read-only DNS queries that retrieve existing records. They do not create, modify, delete, execute code, or trigger external operations. The operation has minimal blast radius even if invoked repeatedly or against many IPs, as it only returns publicly available DNS information. This clearly falls under the Read category.

From the tool's definition Tool description states 'Resolve the PTR (reverse DNS) records for an IP address — the hostname(s) the IP maps back to.' This is a query/lookup operation that retrieves publicly available DNS information with no side effects or modifications.

Questions about reverse_dns

What does the reverse_dns tool do? +

Resolve the PTR (reverse DNS) records for an IP address — the hostname(s) the IP maps back to. Args: - ip (string): IPv4 or IPv6 address. - response_format (. It is categorised as a Read tool in the Domain Security MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on reverse_dns? +

Register the Domain Security MCP server in PolicyLayer and add a rule for reverse_dns: 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 Domain Security. Nothing to install.

What risk level is reverse_dns? +

reverse_dns is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit reverse_dns? +

Yes. Add a rate_limit block to the reverse_dns 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.

How do I block reverse_dns completely? +

Set action: deny in the PolicyLayer policy for reverse_dns. 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.

What MCP server provides reverse_dns? +

reverse_dns is provided by the Domain Security MCP server (ortamarco/domain-security-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.