Low Risk

amass_scan

使用 Amass 执行子域名与资产枚举。

How to control amass_scan ↓

AI agents call amass_scan to retrieve information from Kali Security MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

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.

Documented attack patterns abuse exactly the kind of access amass_scan gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for amass_scan:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "amass_scan": {}
  }
}

amass_scan is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Kali Security MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the amass_scan tool do? +

使用 Amass 执行子域名与资产枚举。. It is categorised as a Read tool in the Kali Security MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on amass_scan? +

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.

What risk level is amass_scan? +

amass_scan is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit amass_scan? +

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.

How do I block amass_scan completely? +

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.

What MCP server provides amass_scan? +

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.

Enforce policy on every Kali Security MCP tool call.

Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.