browser_fill
Clear a field and fill it with text. Use @ref from browser_snapshot. WORKFLOW: browser_snapshot → find input @ref → browser_fill
This record as markdown: /tools/freshdesk/browser-fill.md
What browser_fill does on Freshdesk
AI agents invoke browser_fill 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_fill is rated High
This tool executes browser actions by manipulating UI elements in a live browser session. Filling fields can trigger form submissions, autofill logic, or other side effects depending on the target page. It is an Execute-category action because it drives external browser operations whose effects depend on the arguments supplied (which field, what text).
From the tool's definition 'Clear a field and fill it with text' and 'browser_snapshot → find input @ref → browser_fill' — this tool performs browser UI interactions (clearing and filling form fields) that trigger external browser state changes
Attacks that exploit this kind of access
The rule that runs browser_fill 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_fill, this is the rule to start with:
browser_fill 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_fill call is checked against it from then on.
Questions about browser_fill
Clear a field and fill it with text. Use @ref from browser_snapshot. WORKFLOW: browser_snapshot → find input @ref → browser_fill. 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_fill: 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_fill 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_fill 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_fill. 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_fill 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