browser_tabs
List open tabs or switch to a tab by number.
This record as markdown: /tools/freshdesk/browser-tabs.md
What browser_tabs does on Freshdesk
AI agents call browser_tabs to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why browser_tabs is rated Low
The tool retrieves information about open browser tabs and allows navigation between them. Neither listing nor switching tabs creates, modifies, deletes, or executes arbitrary operations. This is a read-class tool with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'List open tabs or switch to a tab by number' — listing is a read operation; switching to a tab is a state navigation action without data modification or code execution.
Attacks that exploit this kind of access
The rule that runs browser_tabs 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_tabs, this is the rule to start with:
browser_tabs is read-only, so it stays allowed. 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_tabs call is checked against it from then on.
Questions about browser_tabs
List open tabs or switch to a tab by number. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for browser_tabs: 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_tabs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the browser_tabs 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_tabs. 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_tabs 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.
This server
Across the catalogue