chrome_get_feedback_history
Get history of collected feedback from Chrome extension
This record as markdown: /tools/2019-02-18-mcx/chrome-get-feedback-history.md
What chrome_get_feedback_history does on Chrome Feedback
AI agents call chrome_get_feedback_history to retrieve information from Chrome Feedback without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why chrome_get_feedback_history is rated Low
This tool queries and retrieves previously collected feedback data. It performs a simple data retrieval operation analogous to 'get' or 'fetch' without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal — an attacker gains only visibility into historical feedback already submitted, posing no risk to data integrity, system execution, or financial impact.
From the tool's definition Tool name and description: 'Get history of collected feedback' — the verb 'Get' and action 'retrieve history' indicate a read-only retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs chrome_get_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_get_feedback_history, this is the rule to start with:
chrome_get_feedback_history 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 Chrome Feedback, apply this rule, and every chrome_get_feedback_history call is checked against it from then on.
Questions about chrome_get_feedback_history
Get history of collected feedback from Chrome extension. It is categorised as a Read tool in the Chrome Feedback MCP Server, which means it retrieves data without modifying state.
Register the Chrome Feedback MCP server in PolicyLayer and add a rule for chrome_get_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_get_feedback_history 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 chrome_get_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_get_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_get_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.
This server
Across the catalogue