Find elements on the page using natural language. Can search for elements by their purpose (e.g.,
AI agents call find to retrieve information from OpenChrome without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'find' tool retrieves information about page elements using natural language queries. It performs no mutations, executions, or side effects—it only identifies and returns element information. This is a classic Read operation. Low severity because misuse would at most return incorrect element references, which the caller would need to act upon separately via other tools like 'act' to cause actual impact.
From the tool's definition Tool description states 'Find elements on the page' - a query/search operation that locates DOM elements without modifying them. The natural language search capability for elements is a retrieval mechanism.
Documented attack patterns abuse exactly the kind of access find gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenChrome, and nothing reaches the server without passing your rules. This is the rule we recommend for find:
{
"version": "1",
"default": "deny",
"tools": {
"find": {}
}
}find is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find elements on the page using natural language. Can search for elements by their purpose (e.g.,. It is categorised as a Read tool in the OpenChrome MCP Server, which means it retrieves data without modifying state.
Register the OpenChrome MCP server in PolicyLayer and add a rule for find: 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 OpenChrome. Nothing to install.
find 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 find 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 find. 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.
find is provided by the OpenChrome MCP server (shaun0927/openchrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 106 OpenChrome tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
106 OpenChrome tools catalogued and risk-classified — across an index of 42,500+ MCP servers.