theharvester_dns_brute · theHarvester MCP Server MCP

WHAT IT DOES

What theharvester_dns_brute does on theHarvester MCP Server

AI agents invoke theharvester_dns_brute to trigger actions in theHarvester MCP Server. 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.

WHY IT NEEDS A POLICY

Why theharvester_dns_brute needs a policy

This tool actively runs DNS brute force attacks against a target domain using theHarvester on a Kali Linux host via SSH. It executes external network operations (DNS queries in bulk) against third-party infrastructure, which constitutes an active reconnaissance operation.

From the tool's definition Perform DNS brute force enumeration to discover subdomains using a wordlist

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

theharvester_dns_brute Rate-limited

theharvester_dns_brute 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": {
    "theharvester_dns_brute": {
      "limits": [
        {
          "counter": "theharvester_dns_brute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches theHarvester MCP Server, so you can run agents against it safely.

FAQ

Questions about theharvester_dns_brute

What does the theharvester_dns_brute tool do? +

Perform DNS brute force enumeration to discover subdomains using a wordlist. It is categorised as a Execute tool in the theHarvester MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on theharvester_dns_brute? +

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

What risk level is theharvester_dns_brute? +

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

Can I rate-limit theharvester_dns_brute? +

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

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

theharvester_dns_brute is provided by the theHarvester MCP Server MCP server (schwarztim/sec-theharvester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.