http_request

A execute tool on the Pentest Ai MCP server.

SERVERPentest Ai SOURCE0xsteph/pentest-ai

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xsteph-pentest-ai/http-request.md

WHAT IT DOES

What http_request does on Pentest Ai

AI agents invoke http_request to trigger actions in Pentest Ai. 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.

RISK

Why http_request is rated High

The tool name suggests making HTTP requests, which in the context of an autonomous pentesting server would involve sending potentially malicious or probing requests to external targets. The server context ('real security tools, working PoCs') elevates the risk significantly. Empty description lowers confidence but the pentesting context implies active exploitation capability.

From the tool's definition Tool name 'http_request' on a pentest server with 'real security tools' and 'working PoCs'; description is empty/uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs http_request safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pentest Ai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For http_request, this is the rule to start with:

http_request Rate-limited

http_request 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": {
    "http_request": {
      "limits": [
        {
          "counter": "http_request_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pentest Ai, apply this rule, and every http_request call is checked against it from then on.

FAQ

Questions about http_request

What does the http_request tool do? +

http_request is a execute tool on the Pentest Ai MCP server. It is categorised as a Execute tool in the Pentest Ai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on http_request? +

Register the Pentest Ai MCP server in PolicyLayer and add a rule for http_request: 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 Pentest Ai. Nothing to install.

What risk level is http_request? +

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

Can I rate-limit http_request? +

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

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

http_request is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pentest Ai, and thousands of servers like it.

This server

All 51 Pentest Ai tools → High-risk tools on this server →

Across the catalogue

request_elevation on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →