This record as markdown: /tools/seac-25-kali-security-mcp/amass-scan.md
What amass_scan does on Kali Security MCP
AI agents call amass_scan to retrieve information from Kali Security MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why amass_scan is rated Low
Amass is a passive reconnaissance tool that discovers subdomains and maps assets through DNS queries and public data sources. It retrieves information only; enumeration does not alter target systems or data. This is a classic Read operation (reconnaissance/discovery). Severity is low because enumeration itself causes no damage—it's passive intelligence gathering.
From the tool's definition Amass 执行子域名与资产枚举 - the tool performs subdomain and asset enumeration, which is reconnaissance and information gathering without modifying target systems.
Attacks that exploit this kind of access
The rule that runs amass_scan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For amass_scan, this is the rule to start with:
amass_scan is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kali Security MCP, apply this rule, and every amass_scan call is checked against it from then on.
Questions about amass_scan
使用 Amass 执行子域名与资产枚举。. It is categorised as a Read tool in the Kali Security MCP MCP Server, which means it retrieves data without modifying state.
Register the Kali Security MCP server in PolicyLayer and add a rule for amass_scan: 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 Kali Security MCP. Nothing to install.
amass_scan 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_scan 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_scan. 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_scan is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kali Security, and thousands of servers like it.
This server
Across the catalogue