resolve_hostname_to_ip

THE RISK

Low Risk

Why resolve_hostname_to_ip needs a policy

This tool performs a DNS lookup, which is a read-only operation with no side effects. It simply queries DNS to convert a hostname to an IP address. While it is part of a red-teaming server, the operation itself is benign and informational.

From the tool's definition Resolve a hostname to an IP address with timeout

Documented attack patterns abuse exactly the kind of access resolve_hostname_to_ip gives an agent:

POLICY

How to control resolve_hostname_to_ip

PolicyLayer is an MCP gateway — it sits between your AI agents and Red-team-mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for resolve_hostname_to_ip:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_hostname_to_ip": {}
  }
}

resolve_hostname_to_ip is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Red-team-mcp — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Red-team-mcp tools

Execute execute_exploit execute_exploit Execute domain_discovery domain_discovery Execute enumerate_vulnerabilities enumerate_vulnerabilities Execute port_scan port_scan Execute search_exploits search_exploits Write save_hacking_results save_hacking_results Read get_banner get_banner Read get_finished_scan_results get_finished_scan_results

All 13 Red-team-mcp tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about resolve_hostname_to_ip

What does the resolve_hostname_to_ip tool do? +

Resolve a hostname to an IP address with timeout. It is categorised as a Read tool in the Red-team-mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on resolve_hostname_to_ip? +

Register the Red-team- MCP server in PolicyLayer and add a rule for resolve_hostname_to_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 Red-team-mcp. Nothing to install.

What risk level is resolve_hostname_to_ip? +

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

Can I rate-limit resolve_hostname_to_ip? +

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

How do I block resolve_hostname_to_ip completely? +

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

What MCP server provides resolve_hostname_to_ip? +

resolve_hostname_to_ip is provided by the Red-team- MCP server (skjortan23/read-team-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Red-team-mcp tool call.

Start from Red-team-mcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →