Click an element identified by selector.
AI agents use browser_click to create or update resources in Robot Framework MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Robot Framework MCP Server environment.
An AI agent can call browser_click faster than any human can review — one bad instruction and it creates or modifies resources in Robot Framework MCP Server by the hundred, each call as confident as the last.
Documented attack patterns abuse exactly the kind of access browser_click gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Robot Framework MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_click:
{
"version": "1",
"default": "deny",
"tools": {
"browser_click": {
"limits": [
{
"counter": "browser_click_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}browser_click stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Click an element identified by selector. It is categorised as a Write tool in the Robot Framework MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Robot Framework MCP Server MCP server in PolicyLayer and add a rule for browser_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 Robot Framework MCP Server. Nothing to install.
browser_click is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the browser_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 browser_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.
browser_click is provided by the Robot Framework MCP Server MCP server (sourcefuse/robotframework-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 Robot Framework MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 Robot Framework MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.