Make an HTTP request with curl
AI agents invoke make_http_request to trigger actions in Puppeteer 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.
This tool runs curl, an external process, to make HTTP requests to arbitrary endpoints. The effects depend entirely on the arguments: it could read data (GET), write/create data (POST/PUT), delete resources (DELETE), trigger webhooks, or interact with internal network services. Because the behavior and blast radius depend on arguments and it executes an external operation, Execute is the appropriate category.
From the tool's definition 'Make an HTTP request with curl' — executes an external curl command to arbitrary URLs
Attacks that exploit this kind of access
Make an HTTP request with curl. It is categorised as a Execute tool in the Puppeteer MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Puppeteer MCP Server MCP server in PolicyLayer and add a rule for make_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 Puppeteer MCP Server. Nothing to install.
make_http_request 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 make_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.
Set action: deny in the PolicyLayer policy for make_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.
make_http_request is provided by the Puppeteer MCP Server MCP server (jwaldor/mcp-scrape-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →