Click an element by its ref number from the most recent browser_snapshot.
AI agents invoke browser_click_ref to trigger actions in Taw Computer. 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 is an interactive action that triggers external operations (form submissions, navigation, downloads, purchases, etc.) depending on what element is clicked. It's an Execute-category action with medium severity since the blast radius depends on context but could trigger significant side effects.
From the tool's definition Click an element by its ref number from the most recent browser_snapshot
Documented attack patterns abuse exactly the kind of access browser_click_ref gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Taw Computer, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_click_ref:
{
"version": "1",
"default": "deny",
"tools": {
"browser_click_ref": {
"limits": [
{
"counter": "browser_click_ref_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_click_ref 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 by its ref number from the most recent browser_snapshot. It is categorised as a Execute tool in the Taw Computer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Taw Computer MCP server in PolicyLayer and add a rule for browser_click_ref: 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 Taw Computer. Nothing to install.
browser_click_ref 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 browser_click_ref 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_ref. 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_ref is provided by the Taw Computer MCP server (tawgroup/taw-computer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Taw Computer, 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.
36 Taw Computer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.