This record as markdown: /tools/io-github-kivanccakmak-yaver/feedback-delete.md
What feedback_delete does on Yaver
AI agents call feedback_delete to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes |
Parameters from the server's own tool schema.
Why feedback_delete is rated Critical
This tool irreversibly deletes feedback reports, which constitutes a destructive action that cannot be undone. The description itself classifies it as 'Destructive'. The blast radius is high because deletion of feedback data could eliminate important user insights, audit trails, or compliance records, though it does not involve financial transactions or code execution.
From the tool's definition Tool name 'feedback_delete' and description explicitly states 'Remove a feedback report. Destructive.'
Attacks that exploit this kind of access
The rule that runs feedback_delete 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_delete, this is the rule to start with:
feedback_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every feedback_delete call is checked against it from then on.
Questions about feedback_delete
Remove a feedback report. Destructive. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
feedback_delete 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_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the feedback_delete 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_delete. 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_delete 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.
Across the catalogue