Click on an element using CSS selector, text, or role
AI agents invoke interact.click to trigger actions in LCBro. 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.
This tool triggers browser interactions (clicking elements) which can cause external side effects such as form submissions, navigation, triggering downloads, or activating UI actions. The effect depends on what element is clicked, making it an Execute-category action. Misuse could trigger unintended actions on web pages, hence medium severity.
From the tool's definition Click on an element using CSS selector, text, or role
Documented attack patterns abuse exactly the kind of access interact.click gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LCBro, and nothing reaches the server without passing your rules. This is the rule we recommend for interact.click:
{
"version": "1",
"default": "deny",
"tools": {
"interact.click": {
"limits": [
{
"counter": "interact.click_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}interact.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.
Click on an element using CSS selector, text, or role. It is categorised as a Execute tool in the LCBro MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the LCBro MCP server in PolicyLayer and add a rule for interact.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 LCBro. Nothing to install.
interact.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 interact.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 interact.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.
interact.click is provided by the LCBro MCP server (lcbro/lcbro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LCBro, 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.
11 LCBro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.