Find clickable buttons/links, optionally filtered by text.
AI agents call find_clickable_elements to retrieve information from JS Reverse Strong MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool observes and queries the browser's DOM to identify interactive elements. It returns data about what is clickable but does not interact with, modify, or execute anything. This is a pure read operation aligned with browser observation workflows mentioned in the server description. The low severity reflects minimal blast radius—an agent cannot cause harm by simply discovering which elements are clickable.
From the tool's definition Tool name 'find_clickable_elements' combined with description 'Find clickable buttons/links, optionally filtered by text' indicates a query/search operation.
Documented attack patterns abuse exactly the kind of access find_clickable_elements gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JS Reverse Strong MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for find_clickable_elements:
{
"version": "1",
"default": "deny",
"tools": {
"find_clickable_elements": {}
}
}find_clickable_elements 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 clickable buttons/links, optionally filtered by text. It is categorised as a Read tool in the JS Reverse Strong MCP MCP Server, which means it retrieves data without modifying state.
Register the JS Reverse Strong 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 Strong 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 Strong MCP server (lwjjike/jsreverser-strong-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JS Reverse Strong MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
85 JS Reverse Strong MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.