waybackurls_discovery · Bug Bounty MCP Server MCP

WHAT IT DOES

What waybackurls_discovery does on Bug Bounty MCP Server

AI agents invoke waybackurls_discovery 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 waybackurls_discovery needs a policy

The tool runs an external tool (Waybackurls) to perform historical URL discovery. While the primary output is read-only data retrieval from the Wayback Machine, 'Execute' is appropriate because it actively runs an external command/process whose behavior depends on arguments. It's part of a bug bounty reconnaissance workflow and triggers external operations.

From the tool's definition Execute Waybackurls for historical URL discovery with enhanced logging

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

waybackurls_discovery Rate-limited

waybackurls_discovery 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": {
    "waybackurls_discovery": {
      "limits": [
        {
          "counter": "waybackurls_discovery_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 waybackurls_discovery

What does the waybackurls_discovery tool do? +

Execute Waybackurls for historical URL discovery with enhanced logging. 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 waybackurls_discovery? +

Register the Bug Bounty MCP Server MCP server in PolicyLayer and add a rule for waybackurls_discovery: 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 waybackurls_discovery? +

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

Can I rate-limit waybackurls_discovery? +

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

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

waybackurls_discovery 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.