http_request
Make an HTTP request (like curl). Returns status code and response body.
This record as markdown: /tools/io-github-kivanccakmak-yaver/http-request.md
What http_request does on Yaver
AI agents invoke http_request to trigger actions in Yaver. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Request URL |
body | string | — | Request body |
method | string | — | HTTP method (default: GET) |
headers | object | — | Request headers as key-value pairs |
Parameters from the server's own tool schema.
Why http_request is rated High
This tool executes arbitrary HTTP requests to any URL, similar to curl. It can trigger external operations, POST data to APIs, call webhooks, or interact with any networked service.
From the tool's definition Make an HTTP request (like curl). Returns status code and response body.
Risk signalsAccepts URL/endpoint input (url) · Accepts raw HTML/template content (body)
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 Yaver, 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 Yaver, apply this rule, and every http_request call is checked against it from then on.
Questions about http_request
Make an HTTP request (like curl). Returns status code and response body. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
http_request accepts 4 parameters: url, body, method, headers. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver 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 Yaver. 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 Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue