httpx_probe
A execute tool on the Pengstrike MCP server.
This record as markdown: /tools/pengstrike-mcp/httpx-probe.md
What httpx_probe does on Pengstrike
AI agents invoke httpx_probe to trigger actions in Pengstrike. 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 httpx_probe is rated High
httpx is a well-known HTTP probing tool used in security reconnaissance to actively send HTTP requests to targets and gather information. Given the server context (IntelliRecon, browser-native AI recon console) and sibling tools (payload generation, vulnerability assessment, attack suites), this tool almost certainly executes active HTTP probes against external targets.
From the tool's definition Tool name 'httpx_probe' on a security recon server with sibling tools like 'advanced_payload_generation', 'ai_generate_attack_suite', and 'ai_test_payload'. The description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs httpx_probe safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pengstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For httpx_probe, this is the rule to start with:
httpx_probe 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Pengstrike, apply this rule, and every httpx_probe call is checked against it from then on.
Questions about httpx_probe
httpx_probe is a execute tool on the Pengstrike MCP server. It is categorised as a Execute tool in the Pengstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pengstrike 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 Pengstrike. 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 Pengstrike MCP server (wangqiongpeng/pengstrike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pengstrike, and thousands of servers like it.
Across the catalogue