scan_dns_builtin

Perform DNS enumeration (built-in).

SERVERPentest Ai SOURCE0xsteph/pentest-ai

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xsteph-pentest-ai/scan-dns-builtin.md

WHAT IT DOES

What scan_dns_builtin does on Pentest Ai

AI agents invoke scan_dns_builtin to trigger actions in Pentest Ai. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why scan_dns_builtin is rated High

DNS enumeration actively queries external DNS infrastructure to discover hostnames, subdomains, and network topology. This is an active reconnaissance operation with external side effects (sending DNS queries to target systems), placing it in the Execute category. While read-like in intent, it triggers external network operations against target systems, which is characteristic of Execute.

From the tool's definition Perform DNS enumeration (built-in)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scan_dns_builtin safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pentest Ai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scan_dns_builtin, this is the rule to start with:

scan_dns_builtin Rate-limited

scan_dns_builtin stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scan_dns_builtin": {
      "limits": [
        {
          "counter": "scan_dns_builtin_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pentest Ai, apply this rule, and every scan_dns_builtin call is checked against it from then on.

FAQ

Questions about scan_dns_builtin

What does the scan_dns_builtin tool do? +

Perform DNS enumeration (built-in). It is categorised as a Execute tool in the Pentest Ai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scan_dns_builtin? +

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

What risk level is scan_dns_builtin? +

scan_dns_builtin is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit scan_dns_builtin? +

Yes. Add a rate_limit block to the scan_dns_builtin 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 scan_dns_builtin completely? +

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

scan_dns_builtin is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pentest Ai, and thousands of servers like it.

This server

All 51 Pentest Ai tools → High-risk tools on this server →

Across the catalogue

run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →