browser_click
Click an element. Use @ref from browser_snapshot (preferred) or a CSS selector. WORKFLOW: browser_snapshot → find @ref → browser_click @ref
This record as markdown: /tools/freshdesk/browser-click.md
What browser_click does on Freshdesk
AI agents invoke browser_click to trigger actions in Freshdesk. 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.
Why browser_click is rated High
browser_click executes a browser interaction (clicking UI elements), which can trigger arbitrary side effects depending on what is clicked — form submissions, navigation, purchases, deletions, etc. This is a browser automation action classified as Execute.
From the tool's definition 'Click an element' — triggers browser actions whose effects depend on the target element
Attacks that exploit this kind of access
The rule that runs browser_click safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_click, this is the rule to start with:
browser_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every browser_click call is checked against it from then on.
Questions about browser_click
Click an element. Use @ref from browser_snapshot (preferred) or a CSS selector. WORKFLOW: browser_snapshot → find @ref → browser_click @ref. It is categorised as a Execute tool in the Freshdesk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Freshdesk 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 Freshdesk. Nothing to install.
browser_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 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 Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
Across the catalogue