Low Risk

browser_find_elements

Find elements on the page using multiple search criteria such as text, role, tag name, or attributes. Returns matching elements sorted by confidence.

How to control browser_find_elements ↓

AI agents call browser_find_elements to retrieve information from Fast Playwright MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool performs element discovery and inspection only. It queries the DOM to locate and return matching elements based on search criteria (text, role, tag name, attributes), analogous to a selector/search operation. No data is modified, deleted, or executed. The blast radius of misuse is minimal — an agent could query for sensitive information on a page, but cannot take actions or cause irreversible changes.

From the tool's definition Tool description states it 'Find elements on the page' and 'Returns matching elements' — this is a query operation with no side effects.

Documented attack patterns abuse exactly the kind of access browser_find_elements gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Fast Playwright MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_find_elements:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_find_elements": {}
  }
}

browser_find_elements is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Fast Playwright MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the browser_find_elements tool do? +

Find elements on the page using multiple search criteria such as text, role, tag name, or attributes. Returns matching elements sorted by confidence. It is categorised as a Read tool in the Fast Playwright MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_find_elements? +

Register the Fast Playwright MCP server in PolicyLayer and add a rule for browser_find_elements: 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 Fast Playwright MCP. Nothing to install.

What risk level is browser_find_elements? +

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

Can I rate-limit browser_find_elements? +

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

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

browser_find_elements is provided by the Fast Playwright MCP server (tontoko/fast-playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fast Playwright MCP tool call.

Deterministic rules across all 34 Fast Playwright MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

34 Fast Playwright MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.