Passive subdomain enumeration
AI agents call subfinder to retrieve information from PenTest MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Subfinder performs passive reconnaissance by discovering subdomains through DNS records, certificate transparency logs, and other public sources. It retrieves existing data without modifying systems, creating resources, executing code, or deleting anything. This is a classic Read operation—intelligence gathering with no capability to alter state.
From the tool's definition Tool name is 'subfinder' and description states 'Passive subdomain enumeration'. Passive enumeration means it queries public data sources without sending probes to targets, making it purely information retrieval with no side effects.
Attacks that exploit this kind of access
Passive subdomain enumeration. It is categorised as a Read tool in the PenTest MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PenTest MCP Server MCP server in PolicyLayer and add a rule for subfinder: 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 MCP Server. Nothing to install.
subfinder is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the subfinder 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 subfinder. 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.
subfinder is provided by the PenTest MCP Server MCP server (mohitsahoo/mcptoolforwebvulnerabilities-). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →