ultimate_recon · Bug Bounty Hunter MCP: Risk & Policy

WHAT IT DOES

What ultimate_recon does on Bug Bounty Hunter MCP

AI agents invoke ultimate_recon to trigger actions in Bug Bounty Hunter MCP. 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 ultimate_recon needs a policy

This tool actively runs an extensive multi-stage reconnaissance workflow against external targets (subdomain enumeration, OSINT gathering, DNS probing, etc.), consistent with the server's stated capabilities. It is not merely reading local data — it triggers external network operations whose effects depend on the target argument.

From the tool's definition 'Executes a God Level reconnaissance workflow' — the word 'Executes' confirms active operation; 'God Level' implies comprehensive, wide-ranging external probing across multiple recon techniques

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ultimate_recon Rate-limited

ultimate_recon 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": {
    "ultimate_recon": {
      "limits": [
        {
          "counter": "ultimate_recon_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 Hunter MCP, so you can run agents against it safely.

FAQ

Questions about ultimate_recon

What does the ultimate_recon tool do? +

Executes a 'God Level' reconnaissance workflow. It is categorised as a Execute tool in the Bug Bounty Hunter MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ultimate_recon? +

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

What risk level is ultimate_recon? +

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

Can I rate-limit ultimate_recon? +

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

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

ultimate_recon is provided by the Bug Bounty Hunter MCP server (mauricioduarte100/bugbountymcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.