browser_get_page_info

Get the current page URL and title.

SERVERFreshdesk SOURCE@mindstone-engineering/mcp-server-freshdesk

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/freshdesk/browser-get-page-info.md

WHAT IT DOES

What browser_get_page_info does on Freshdesk

AI agents call browser_get_page_info 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.

RISK

Why browser_get_page_info is rated Low

This tool only retrieves information (URL and title) from the current browser page without modifying, deleting, or executing any operations. It is a straightforward read operation with minimal security risk.

From the tool's definition Tool name is 'browser_get_page_info' and description states it will 'Get the current page URL and title.' This retrieves metadata about the current browser state with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_get_page_info 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_get_page_info, this is the rule to start with:

browser_get_page_info Allowed

browser_get_page_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_get_page_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every browser_get_page_info call is checked against it from then on.

FAQ

Questions about browser_get_page_info

What does the browser_get_page_info tool do? +

Get the current page URL and title. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_get_page_info? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for browser_get_page_info: 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.

What risk level is browser_get_page_info? +

browser_get_page_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_get_page_info? +

Yes. Add a rate_limit block to the browser_get_page_info 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.

How do I block browser_get_page_info completely? +

Set action: deny in the PolicyLayer policy for browser_get_page_info. 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.

What MCP server provides browser_get_page_info? +

browser_get_page_info 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.

KEEP EXPLORING

More on Freshdesk, and thousands of servers like it.

This server

All 422 Freshdesk tools →

Across the catalogue

get_team_info on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →