Advanced subdomain enumeration
AI agents call amass 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.
Subdomain enumeration collects information about a target's infrastructure through passive and semi-passive DNS queries. This is fundamentally a Read operation: it retrieves and lists subdomains associated with a domain. While it is a reconnaissance tool used in penetration testing, it does not execute code on systems, modify data, delete resources, or make financial transactions.
From the tool's definition Tool name 'amass' with description 'Advanced subdomain enumeration' - enumeration is purely a reconnaissance/discovery activity that queries DNS and WHOIS data without modifying anything or triggering external actions beyond standard DNS queries.
Attacks that exploit this kind of access
Advanced 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 amass: 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.
amass 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 amass 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 amass. 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.
amass 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 →