arjun_parameter_discovery · Bug Bounty MCP Server MCP

WHAT IT DOES

What arjun_parameter_discovery does on Bug Bounty MCP Server

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

This tool actively runs the Arjun tool against external targets to discover HTTP parameters. It triggers an external security scanning operation whose effects depend on the target arguments provided. This constitutes active reconnaissance against external systems, which can be intrusive and potentially unauthorized.

From the tool's definition Execute Arjun for HTTP parameter discovery

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

arjun_parameter_discovery Rate-limited

arjun_parameter_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": {
    "arjun_parameter_discovery": {
      "limits": [
        {
          "counter": "arjun_parameter_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 arjun_parameter_discovery

What does the arjun_parameter_discovery tool do? +

Execute Arjun for HTTP parameter 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 arjun_parameter_discovery? +

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

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

Can I rate-limit arjun_parameter_discovery? +

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

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

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