AI agents invoke element_click to trigger actions in DrissionPageMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Clicking a browser element can trigger arbitrary side effects depending on what is clicked: form submissions, navigation, purchases, deletions, or any other web action. This is a browser automation Execute action with high blast radius since an AI agent could click destructive or financial UI elements.
From the tool's definition 点击标签页中某个元素 (click an element in a tab via xpath) — triggers browser click actions whose effects depend on the target element
Documented attack patterns abuse exactly the kind of access element_click 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 element_click:
{
"version": "1",
"default": "deny",
"tools": {
"element_click": {
"limits": [
{
"counter": "element_click_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}element_click stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
通过xpath点击标签页中某个元素,最好先判断元素是否存在. It is categorised as a Execute tool in the DrissionPageMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DrissionPage MCP server in PolicyLayer and add a rule for element_click: 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.
element_click is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the element_click 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 element_click. 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.
element_click 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.