amass_scan

Execute Amass for subdomain enumeration with enhanced logging.

SERVERPengstrike SOURCEwangqiongpeng/pengstrike-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/pengstrike-mcp/amass-scan.md

WHAT IT DOES

What amass_scan does on Pengstrike

AI agents invoke amass_scan to trigger actions in Pengstrike. 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.

RISK

Why amass_scan is rated High

This tool runs the Amass external binary/process to perform active subdomain enumeration against a target. It triggers an external network reconnaissance operation, making it Execute category. The blast radius is high because an AI agent could use it to conduct unauthorized reconnaissance against arbitrary targets, potentially violating laws (CFAA, etc.) and exposing the operator to legal liability.

From the tool's definition Execute Amass for subdomain enumeration with enhanced logging

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs amass_scan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pengstrike, 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 Rate-limited

amass_scan stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "amass_scan": {
      "limits": [
        {
          "counter": "amass_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pengstrike, apply this rule, and every amass_scan call is checked against it from then on.

FAQ

Questions about amass_scan

What does the amass_scan tool do? +

Execute Amass for subdomain enumeration with enhanced logging. It is categorised as a Execute tool in the Pengstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on amass_scan? +

Register the Pengstrike 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 Pengstrike. Nothing to install.

What risk level is amass_scan? +

amass_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

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 Pengstrike MCP server (wangqiongpeng/pengstrike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pengstrike, and thousands of servers like it.

This server

All 163 Pengstrike tools → High-risk tools on this server →

Across the catalogue

run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →