web_find
Finds elements on the current page of a web session so you can decide what to click or type into. query is a CSS selector OR visible text to match. Returns up to 30 matches with tag/text/name/type/href — never a silent empty.
This record as markdown: /tools/com-local-mcp-local-mcp/web-find.md
What web_find does on Local
AI agents call web_find to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | A CSS selector (e.g. 'input[name=q]') or visible text (e.g. 'Sign in'). |
session | string | — | Session name (default 'default'). |
Parameters from the server's own tool schema.
Why web_find is rated Low
This is a query/search operation that reads and returns DOM element data. It has no side effects on the page state, data, or external systems. The tool is informational only, used to locate elements for subsequent actions by other tools. Low severity because misuse would only expose page structure information, not cause harm.
From the tool's definition Tool description states it 'Finds elements on the current page' and 'Returns up to 30 matches with tag/text/name/type/href' — it retrieves information about page elements without modifying, deleting, or executing actions.
Attacks that exploit this kind of access
The rule that runs web_find safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For web_find, this is the rule to start with:
web_find 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 Local, apply this rule, and every web_find call is checked against it from then on.
Questions about web_find
Finds elements on the current page of a web session so you can decide what to click or type into. query is a CSS selector OR visible text to match. Returns up to 30 matches with tag/text/name/type/href — never a silent empty. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
web_find accepts 2 parameters: query, session. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for web_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 Local. Nothing to install.
web_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 web_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 web_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.
web_find is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue