# chrome_clear_feedback_history

Clear all Chrome extension feedback history

Agent View of the PolicyLayer registry record for `chrome_clear_feedback_history`. HTML page: https://policylayer.com/tools/2019-02-18-mcx/chrome-clear-feedback-history

## Facts

- Tool: `chrome_clear_feedback_history`
- Server: Chrome Feedback (`2019-02-18/mcx`) — https://policylayer.com/tools/2019-02-18-mcx.md
- Homepage: https://github.com/2019-02-18/MCX
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "chrome_clear_feedback_history",
    "arguments": {}
  }
}
```

## 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 own 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 signals: Bulk/mass operation — affects multiple targets

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Chrome Feedback:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "chrome_clear_feedback_history"
  ]
}
```

## Other tools on Chrome Feedback (15)

- `chrome_click_element` — Execute — https://policylayer.com/tools/2019-02-18-mcx/chrome-click-element.md
- `chrome_execute_script` — Execute — https://policylayer.com/tools/2019-02-18-mcx/chrome-execute-script.md
- `chrome_fill_input` — Execute — https://policylayer.com/tools/2019-02-18-mcx/chrome-fill-input.md
- `chrome_interact_element` — Execute — https://policylayer.com/tools/2019-02-18-mcx/chrome-interact-element.md
- `chrome_navigate_to_url` — Execute — https://policylayer.com/tools/2019-02-18-mcx/chrome-navigate-to-url.md
- `chrome_wait_for_element` — Execute — https://policylayer.com/tools/2019-02-18-mcx/chrome-wait-for-element.md
- `chrome_analyze_form_structure` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-analyze-form-structure.md
- `chrome_extract_content` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-extract-content.md
- `chrome_get_extension_status` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-get-extension-status.md
- `chrome_get_feedback_history` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-get-feedback-history.md
- `chrome_get_page_info` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-get-page-info.md
- `chrome_interactive_feedback` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-interactive-feedback.md
- `chrome_smart_locate_element` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-smart-locate-element.md
- `chrome_take_screenshot` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-take-screenshot.md
- `chrome_fill_form` — Write — https://policylayer.com/tools/2019-02-18-mcx/chrome-fill-form.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=2019-02-18-mcx · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/2019-02-18-mcx