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

chrome_interactive_feedback

Request interactive feedback from user through Chrome extension interface

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-interactive-feedback.md

What chrome_interactive_feedback does on Chrome Feedback

AI agents call chrome_interactive_feedback 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_interactive_feedback is rated Low

This tool requests feedback from a user through a UI interface. It collects data (reads user input) but does not execute commands, modify system state, delete data, or trigger financial operations.

From the tool's definition Tool description states 'Request interactive feedback from user through Chrome extension interface' - this is a request for user input, which is a read operation that retrieves user-provided feedback without modifying system state or triggering external…

Questions about chrome_interactive_feedback

What does the chrome_interactive_feedback tool do? +

Request interactive feedback from user through Chrome extension interface. 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_interactive_feedback? +

Register the Chrome Feedback MCP server in PolicyLayer and add a rule for chrome_interactive_feedback: 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_interactive_feedback? +

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

Can I rate-limit chrome_interactive_feedback? +

Yes. Add a rate_limit block to the chrome_interactive_feedback 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_interactive_feedback completely? +

Set action: deny in the PolicyLayer policy for chrome_interactive_feedback. 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_interactive_feedback? +

chrome_interactive_feedback 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

// 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.