amass_enum · Redteam MCP: Risk & Policy

WHAT IT DOES

What amass_enum does on Redteam

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

WHY IT NEEDS A POLICY

Why amass_enum needs a policy

Amass performs active DNS enumeration and attack surface mapping against external targets. This is an active reconnaissance tool that sends network probes and queries to third-party systems, constituting execution of external operations. While primarily read-like in intent, it actively interacts with target infrastructure and is part of a penetration testing/hacking toolkit, elevating severity.

From the tool's definition 'Perform in-depth DNS enumeration and attack surface mapping with Amass' running inside a Kali Linux Docker container for penetration testing

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

amass_enum Rate-limited

amass_enum 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_enum": {
      "limits": [
        {
          "counter": "amass_enum_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Redteam, so you can run agents against it safely.

FAQ

Questions about amass_enum

What does the amass_enum tool do? +

Perform in-depth DNS enumeration and attack surface mapping with Amass. It is categorised as a Execute tool in the Redteam 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_enum? +

Register the Redteam MCP server in PolicyLayer and add a rule for amass_enum: 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 Redteam. Nothing to install.

What risk level is amass_enum? +

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

Can I rate-limit amass_enum? +

Yes. Add a rate_limit block to the amass_enum 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_enum completely? +

Set action: deny in the PolicyLayer policy for amass_enum. 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_enum? +

amass_enum is provided by the Redteam MCP server (samirjani03/redteam-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.