error_list
List cross-device error records aggregated from every SDK session. Each record has a fingerprint, message, count, device list, and recent samples.
This record as markdown: /tools/io-github-kivanccakmak-yaver/error-list.md
What error_list does on Yaver
AI agents call error_list 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 |
|---|---|---|---|
include_resolved | boolean | — | Include resolved errors in the list |
Parameters from the server's own tool schema.
Why error_list is rated Low
This tool retrieves and lists error telemetry data aggregated across devices and SDK sessions. It has no side effects: it does not create, modify, delete, execute code, or move money. The operation is purely informational—fetching existing error records for diagnostics and monitoring purposes.
From the tool's definition Tool name is 'error_list' and description states it 'List cross-device error records' — a read-only retrieval operation that queries and aggregates error data without modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs error_list 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 error_list, this is the rule to start with:
error_list 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 error_list call is checked against it from then on.
Questions about error_list
List cross-device error records aggregated from every SDK session. Each record has a fingerprint, message, count, device list, and recent samples. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
error_list accepts 1 parameter: include_resolved. 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 error_list: 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.
error_list 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 error_list 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 error_list. 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.
error_list 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