feedback_list
List recent feedback reports captured from the Feedback SDK (React Native / Flutter / Web). Includes crash logs, screenshots, black-box ring buffers.
This record as markdown: /tools/io-github-kivanccakmak-yaver/feedback-list.md
What feedback_list does on Yaver
AI agents call feedback_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 |
|---|---|---|---|
limit | integer | — | Max items to return. Default 20. |
Parameters from the server's own tool schema.
Why feedback_list is rated Low
This tool retrieves and displays feedback reports and diagnostics from a mobile/web app's feedback system. It performs a read-only query operation that has no side effects on the feedback data or system state. The blast radius of misuse is low—an agent could only access feedback/diagnostics already captured by the app, not alter, delete, or trigger external operations.
From the tool's definition Tool description explicitly states 'List recent feedback reports' — the verb 'list' indicates retrieval/querying of existing data with no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs feedback_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 feedback_list, this is the rule to start with:
feedback_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 feedback_list call is checked against it from then on.
Questions about feedback_list
List recent feedback reports captured from the Feedback SDK (React Native / Flutter / Web). Includes crash logs, screenshots, black-box ring buffers. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
feedback_list accepts 1 parameter: limit. 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 feedback_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.
feedback_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 feedback_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 feedback_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.
feedback_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