http_client
Universal HTTP request to any API/webhook (300 sats/call; free tier 100 calls/mo)
This record as markdown: /tools/com-thetempleofdoom-hyperion-hyperion/http-client.md
What http_client does on Hyperion
AI agents call http_client to retrieve information from Hyperion without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Target request URL. |
body | string | — | Stringified JSON or text body for POST/PUT/PATCH. |
method | string | — | HTTP method (default GET). |
headers | object | — | Key-value object of request headers. |
timeoutMs | number | — | Request timeout in milliseconds (default 5000). |
Parameters from the server's own tool schema.
Why http_client is rated Low
Even though http_client only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts URL/endpoint input (url) · Accepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs http_client safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hyperion, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For http_client, this is the rule to start with:
http_client is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hyperion, apply this rule, and every http_client call is checked against it from then on.
Questions about http_client
Universal HTTP request to any API/webhook (300 sats/call; free tier 100 calls/mo). It is categorised as a Read tool in the Hyperion MCP Server, which means it retrieves data without modifying state.
http_client accepts 5 parameters: url, body, method, headers, timeoutMs. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Hyperion MCP server in PolicyLayer and add a rule for http_client: 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 Hyperion. Nothing to install.
http_client is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the http_client 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_client. 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_client is provided by the Hyperion MCP server (https://hyperion.thetempleofdoom.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hyperion, and thousands of servers like it.
This server
Across the catalogue