chrome_interact_element

Perform various interactions with DOM elements (click, hover, select, etc.)

SERVERChrome Feedback SOURCE2019-02-18/mcx

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/2019-02-18-mcx/chrome-interact-element.md

WHAT IT DOES

What chrome_interact_element does on Chrome Feedback

AI agents invoke chrome_interact_element to trigger actions in Chrome Feedback. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why chrome_interact_element is rated High

This tool triggers real browser interactions on DOM elements such as clicking, hovering, and selecting. These are active browser actions that can trigger event handlers, form submissions, navigation, or other side effects depending on the page context. The effects are determined by the arguments (which element and what action), making this an Execute-category tool.

From the tool's definition Perform various interactions with DOM elements (click, hover, select, etc.)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs chrome_interact_element 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_interact_element, this is the rule to start with:

chrome_interact_element Rate-limited

chrome_interact_element stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "chrome_interact_element": {
      "limits": [
        {
          "counter": "chrome_interact_element_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Feedback, apply this rule, and every chrome_interact_element call is checked against it from then on.

FAQ

Questions about chrome_interact_element

What does the chrome_interact_element tool do? +

Perform various interactions with DOM elements (click, hover, select, etc.). It is categorised as a Execute tool in the Chrome Feedback MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on chrome_interact_element? +

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

chrome_interact_element is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit chrome_interact_element? +

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

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

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

KEEP EXPLORING

More on Chrome Feedback, and thousands of servers like it.

This server

All 16 Chrome Feedback tools → High-risk tools on this server →

Across the catalogue

browser_wait_for_element on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →