http_request
Make HTTP requests like curl. Supports all HTTP methods, custom headers, and request bodies.
This record as markdown: /tools/cowork-os/http-request.md
What http_request does on CoWork OS
AI agents invoke http_request to trigger actions in CoWork OS. 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 http_request is rated High
This tool can send arbitrary HTTP requests (GET, POST, PUT, DELETE, PATCH, etc.) to any URL with custom headers and bodies. This is an Execute-level tool because it triggers external operations whose effects depend entirely on the arguments — it could interact with internal services, external APIs, webhooks, or even destructive/financial endpoints.
From the tool's definition 'Make HTTP requests like curl. Supports all HTTP methods, custom headers, and request bodies.'
Attacks that exploit this kind of access
The rule that runs http_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, 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 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 CoWork OS, apply this rule, and every http_request call is checked against it from then on.
Questions about http_request
Make HTTP requests like curl. Supports all HTTP methods, custom headers, and request bodies. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CoWork OS 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 CoWork OS. Nothing to install.
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 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 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.
http_request is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
Across the catalogue