AI agents invoke click-element to trigger actions in WDIO MCP Server. 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 an element is a browser automation action whose effects depend entirely on the target element. It could submit forms, trigger navigation, initiate transactions, or cause other side effects. This makes it an Execute-category tool, not a simple Read or Write operation.
From the tool's definition 'Click an element in the active browser' — triggers a browser interaction/action that can have external side effects depending on what element is clicked (form submissions, navigation, purchases, etc.)
Documented attack patterns abuse exactly the kind of access click-element gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WDIO MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for click-element:
{
"version": "1",
"default": "deny",
"tools": {
"click-element": {
"limits": [
{
"counter": "click-element_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}click-element 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.
Click an element in the active browser. It is categorised as a Execute tool in the WDIO MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WDIO MCP Server MCP server in PolicyLayer and add a rule for click-element: 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 WDIO MCP Server. Nothing to install.
click-element 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 click-element 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 click-element. 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.
click-element is provided by the WDIO MCP Server MCP server (siri100/wdio-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WDIO MCP Server, 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.
7 WDIO MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.