httpx_probe
AI agents invoke httpx_probe 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.
The tool name 'httpx_probe' strongly implies active HTTP probing/scanning of external targets using the httpx tool, which sends HTTP requests to discover live hosts and services. This constitutes executing external operations against targets. Severity is high because misuse could probe unauthorized targets. Confidence is reduced because the description is empty, requiring inference from context.
From the tool's definition Tool name 'httpx_probe' suggests active HTTP probing of targets; part of a bug bounty security assessment server with sibling tools like amass_scan, arjun_parameter_discovery, and vulnerability hunting
Attacks that exploit this kind of access
httpx_probe. 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.
Register the Bug Bounty MCP Server MCP server in PolicyLayer and add a rule for httpx_probe: 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.
httpx_probe is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the httpx_probe 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.
Set action: deny in the PolicyLayer policy for httpx_probe. 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.
httpx_probe 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.
httpx_probe is one line of Bug Bounty MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →