subfinder_scan · Bug Bounty MCP Server MCP: Risk & Policy

WHAT IT DOES

What subfinder_scan does on Bug Bounty MCP Server

AI agents invoke subfinder_scan to trigger actions in Bug Bounty 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.

WHY IT NEEDS A POLICY

Why subfinder_scan needs a policy

Subfinder is a well-known subdomain discovery tool that actively queries external DNS resolvers, APIs, and other sources. Despite the empty description, the tool name and server context strongly imply it executes an active reconnaissance scan against external targets. This constitutes an Execute-category action with high severity due to potential for unauthorized scanning of third-party infrastructure.

From the tool's definition Tool name 'subfinder_scan' on a bug bounty server with sibling tools like amass_scan, arjun_parameter_discovery, and bugbounty_reconnaissance_workflow — all of which are active scanning/execution tools.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

subfinder_scan Rate-limited

subfinder_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": {
    "subfinder_scan": {
      "limits": [
        {
          "counter": "subfinder_scan_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 Bug Bounty MCP Server, so you can run agents against it safely.

FAQ

Questions about subfinder_scan

What does the subfinder_scan tool do? +

subfinder_scan. It is categorised as a Execute tool in the Bug Bounty MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on subfinder_scan? +

Register the Bug Bounty MCP Server MCP server in PolicyLayer and add a rule for subfinder_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 Bug Bounty MCP Server. Nothing to install.

What risk level is subfinder_scan? +

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

Can I rate-limit subfinder_scan? +

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

Set action: deny in the PolicyLayer policy for subfinder_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 subfinder_scan? +

subfinder_scan is provided by the Bug Bounty MCP Server MCP server (slanycukr/bugbounty-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.