Find clickable buttons/links, optionally filtered by text.
AI agents call find_clickable_elements to retrieve information from JS Reverse MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the DOM to identify interactive elements but does not interact with them, modify page state, or execute code. It is purely informational. While the sibling tool 'click_element' would be Execute, this tool itself only discovers and returns information about clickable elements, making it a benign Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'find_clickable_elements' and description 'Find clickable buttons/links, optionally filtered by text' indicate data retrieval without modification. The verb 'find' and the passive action of locating DOM elements are characteristic of read operations.
Attacks that exploit this kind of access
Find clickable buttons/links, optionally filtered by text. It is categorised as a Read tool in the JS Reverse MCP MCP Server, which means it retrieves data without modifying state.
Register the JS Reverse MCP server in PolicyLayer and add a rule for find_clickable_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 JS Reverse MCP. Nothing to install.
find_clickable_elements 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_clickable_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.
Set action: deny in the PolicyLayer policy for find_clickable_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.
find_clickable_elements is provided by the JS Reverse MCP server (noone-hub/jsreverser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →