AI agents call get_all_clickable_elements to retrieve information from DrissionPageMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of clickable elements from the current browser page. It performs a read-only query of the DOM structure and returns results without side effects. The capability is informational only—it enables AI to discover what can be clicked but does not perform the click action itself (that is handled by 'element_click' on the same server). Misuse would have minimal impact as no state change occurs.
From the tool's definition Tool name 'get_all_clickable_elements' and description '获取当前标签页的所有可点击元素' (Get all clickable elements of the current page) indicate pure information retrieval.
Documented attack patterns abuse exactly the kind of access get_all_clickable_elements gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DrissionPageMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_all_clickable_elements:
{
"version": "1",
"default": "deny",
"tools": {
"get_all_clickable_elements": {}
}
}get_all_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.
获取当前标签页的所有可点击元素. It is categorised as a Read tool in the DrissionPageMCP MCP Server, which means it retrieves data without modifying state.
Register the DrissionPage MCP server in PolicyLayer and add a rule for get_all_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 DrissionPageMCP. Nothing to install.
get_all_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 get_all_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 get_all_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.
get_all_clickable_elements is provided by the DrissionPage MCP server (wxhzhwxhzh/drissionpagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 37 DrissionPageMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
37 DrissionPageMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.