crow_browser_discover_selectors
Dump all interactive elements on the page (inputs, buttons, links, selects) with their attributes.
This record as markdown: /tools/kh0pper-crow/crow-browser-discover-selectors.md
What crow_browser_discover_selectors does on Crow
AI agents call crow_browser_discover_selectors to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crow_browser_discover_selectors is rated Low
The tool performs read-only introspection of the DOM to enumerate interactive elements and their attributes. While this information could be used to inform subsequent actions (e.g., which buttons to click), the tool itself has no side effects — it only queries and returns data about the current page state. This is analogous to a search or list operation.
From the tool's definition Tool description states it 'Dump[s] all interactive elements on the page (inputs, buttons, links, selects) with their attributes' — this is a passive discovery/inspection operation that retrieves information about page structure without modifying, deleting,…
Attacks that exploit this kind of access
The rule that runs crow_browser_discover_selectors safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_browser_discover_selectors, this is the rule to start with:
crow_browser_discover_selectors 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 Crow, apply this rule, and every crow_browser_discover_selectors call is checked against it from then on.
Questions about crow_browser_discover_selectors
Dump all interactive elements on the page (inputs, buttons, links, selects) with their attributes. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_browser_discover_selectors: 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 Crow. Nothing to install.
crow_browser_discover_selectors 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 crow_browser_discover_selectors 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 crow_browser_discover_selectors. 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.
crow_browser_discover_selectors is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue