This record as markdown: /tools/io-github-kivanccakmak-yaver/http-status.md
What http_status does on Yaver
AI agents call http_status to retrieve information from Yaver 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 |
|---|---|---|---|
code | integer | Yes | HTTP status code (e.g. 418) |
Parameters from the server's own tool schema.
Why http_status is rated Low
This tool performs a simple informational lookup of HTTP status codes. It has no side effects, does not execute code, does not modify data, and does not access or control external systems. The blast radius of misuse is minimal—an agent could only waste resources querying the same status codes repeatedly. It clearly falls under the Read category.
From the tool's definition Tool name and description indicate a lookup operation: 'Look up what an HTTP status code means.' This is a read-only query that retrieves informational content without modifying state or triggering external effects.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs http_status 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_status, this is the rule to start with:
http_status 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 Yaver, apply this rule, and every http_status call is checked against it from then on.
Questions about http_status
Look up what an HTTP status code means. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
http_status accepts 1 parameter: code. Required: code. 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_status: 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_status 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_status 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_status. 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_status 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.
This server
Across the catalogue