amass_scan
AI agents invoke amass_scan to trigger actions in Kali Linux 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.
Amass is a well-known OSINT and network enumeration tool used for attack surface mapping and subdomain discovery. While the description is empty, the tool name and server context strongly suggest it performs active or passive reconnaissance against external targets. On a pentest server alongside exploitation and attack tools, misuse could expose target infrastructure details or be used as a precursor to attacks.
From the tool's definition Tool name 'amass_scan' on a Kali Linux penetration testing server with sibling tools including network scanners, exploitation frameworks, and attack tools.
Attacks that exploit this kind of access
amass_scan. It is categorised as a Execute tool in the Kali Linux MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Linux MCP Server 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 Linux MCP Server. Nothing to install.
amass_scan 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 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 Linux MCP Server MCP server (ofryma/custom-mcp-library). 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 →