This record as markdown: /tools/io-github-kivanccakmak-yaver/http-timing.md
What http_timing does on Yaver
AI agents call http_timing 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 |
|---|---|---|---|
url | string | Yes | URL to measure |
Parameters from the server's own tool schema.
Why http_timing is rated Low
This is a passive measurement and information-retrieval tool. It observes HTTP response times and collects basic metadata, which are read-only operations. There is no code execution, data modification, deletion, or financial impact. The blast radius of misuse is minimal – worst case an attacker learns response times of endpoints, which is low-severity reconnaissance.
From the tool's definition 'Measure HTTP response time and get basic info' – the tool queries/retrieves HTTP metrics and basic information without modifying, executing, or deleting data.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs http_timing 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_timing, this is the rule to start with:
http_timing 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_timing call is checked against it from then on.
Questions about http_timing
Measure HTTP response time and get basic info. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
http_timing accepts 1 parameter: url. 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_timing: 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_timing 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_timing 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_timing. 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_timing 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