Bruteforce subdomains using dnsrecon and custom wordlist.
AI agents invoke bruteforce_subdomains to trigger actions in External Reconnaissance 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.
While reconnaissance itself is not inherently destructive, bruteforce_subdomains actively executes external tools and potentially large-scale reconnaissance operations that could trigger rate-limiting, IDS alerts, or network monitoring. This exceeds passive data retrieval (Read) and enters Execute territory because it runs external commands/tools with effects dependent on the target.
From the tool's definition Tool performs 'bruteforce' operations using external tools (dnsrecon) and wordlists against target domains.
Documented attack patterns abuse exactly the kind of access bruteforce_subdomains gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and External Reconnaissance MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for bruteforce_subdomains:
{
"version": "1",
"default": "deny",
"tools": {
"bruteforce_subdomains": {
"limits": [
{
"counter": "bruteforce_subdomains_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}bruteforce_subdomains 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.
Free to start. No card required.
Bruteforce subdomains using dnsrecon and custom wordlist. It is categorised as a Execute tool in the External Reconnaissance MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the External Reconnaissance MCP Server MCP server in PolicyLayer and add a rule for bruteforce_subdomains: 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 External Reconnaissance MCP Server. Nothing to install.
bruteforce_subdomains is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the bruteforce_subdomains 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 bruteforce_subdomains. 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.
bruteforce_subdomains is provided by the External Reconnaissance MCP Server MCP server (naebo/mcp-external-recon-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from External Reconnaissance MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 External Reconnaissance MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.