chrome_interactive_feedback
Request interactive feedback from user through Chrome extension interface
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…
Attacks that exploit this kind of access
The rule that runs chrome_interactive_feedback 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_interactive_feedback, this is the rule to start with:
chrome_interactive_feedback 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_interactive_feedback call is checked against it from then on.
Questions about chrome_interactive_feedback
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.
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.
chrome_interactive_feedback 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_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.
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.
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.
This server
Across the catalogue