New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

chrome_get_feedback_history

Get history of collected feedback from Chrome extension

SERVERChrome Feedback SOURCE2019-02-18/mcx
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about chrome_get_feedback_history

What does the chrome_get_feedback_history tool do? +

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.

How do I enforce a policy on chrome_get_feedback_history? +

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.

What risk level is chrome_get_feedback_history? +

chrome_get_feedback_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit chrome_get_feedback_history? +

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.

How do I block chrome_get_feedback_history completely? +

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.

What MCP server provides chrome_get_feedback_history? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Chrome Feedback's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.