feedback_show
Return the full feedback report for one id: error metadata, stack, screenshot URL, and a recent-events snapshot from the BlackBox.
This record as markdown: /tools/io-github-kivanccakmak-yaver/feedback-show.md
What feedback_show does on Yaver
AI agents call feedback_show 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 |
|---|---|---|---|
id | string | Yes |
Parameters from the server's own tool schema.
Why feedback_show is rated Low
feedback_show retrieves and displays diagnostic information (error metadata, stack traces, screenshots, event logs) without altering, deleting, or executing anything. This is a read-only query operation with no side effects. Severity is low because the data returned is debugging/diagnostic information scoped to a specific feedback ID, posing minimal risk even if retrieved inappropriately.
From the tool's definition Tool returns data: 'full feedback report for one id: error metadata, stack, screenshot URL, and a recent-events snapshot'. No modification, deletion, or execution occurs.
Attacks that exploit this kind of access
The rule that runs feedback_show 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_show, this is the rule to start with:
feedback_show 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_show call is checked against it from then on.
Questions about feedback_show
Return the full feedback report for one id: error metadata, stack, screenshot URL, and a recent-events snapshot from the BlackBox. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
feedback_show accepts 1 parameter: id. Required: id. 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_show: 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_show 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_show 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_show. 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_show 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