chrome_clear_feedback_history
Clear all Chrome extension feedback history
This record as markdown: /tools/2019-02-18-mcx/chrome-clear-feedback-history.md
What chrome_clear_feedback_history does on Chrome Feedback
AI agents call chrome_clear_feedback_history to permanently remove resources in Chrome Feedback, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why chrome_clear_feedback_history is rated Critical
This tool irreversibly deletes user feedback data in bulk. Once cleared, the history cannot be recovered. This fits the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' Severity is high because loss of feedback history could impact compliance, auditing, or user support workflows, though the blast radius is limited to feedback data rather than critical…
From the tool's definition Tool description explicitly states "Clear all Chrome extension feedback history" — a permanent, irreversible deletion operation that removes all historical feedback data without undo capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs chrome_clear_feedback_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Feedback, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chrome_clear_feedback_history, this is the rule to start with:
chrome_clear_feedback_history 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 Chrome Feedback, apply this rule, and every chrome_clear_feedback_history call is checked against it from then on.
Questions about chrome_clear_feedback_history
Clear all Chrome extension feedback history. It is categorised as a Destructive tool in the Chrome Feedback MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Chrome Feedback MCP server in PolicyLayer and add a rule for chrome_clear_feedback_history: 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 Chrome Feedback. Nothing to install.
chrome_clear_feedback_history 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 chrome_clear_feedback_history 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 chrome_clear_feedback_history. 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.
chrome_clear_feedback_history is provided by the Chrome Feedback MCP server (2019-02-18/mcx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome Feedback, and thousands of servers like it.
Across the catalogue