Retrieve comprehensive information about the current browser state including current URL, page title, number of open tabs, and details about each tab. Essential for understanding where you are in a multi-step process, confirming navigation worked, or deciding which tab to switch to. Returns list ...
AI agents call get_current_page_info to retrieve information from WebScout MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about the browser's current state (URL, page title, tabs). It performs no modifications, deletions, code execution, or financial operations. It is purely informational/observational, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'get_current_page_info' and description states it 'Retrieve[s] comprehensive information about the current browser state' and 'Returns list of all tabs with their URLs, titles, and which one is currently active.' The verb 'retrieve' and the…
Attacks that exploit this kind of access
Retrieve comprehensive information about the current browser state including current URL, page title, number of open tabs, and details about each tab. Essential for understanding where you are in a multi-step process, confirming navigation worked, or deciding which tab to switch to. Returns list of all tabs with their URLs, titles, and which one is currently active. It is categorised as a Read tool in the WebScout MCP MCP Server, which means it retrieves data without modifying state.
Register the WebScout MCP server in PolicyLayer and add a rule for get_current_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 WebScout MCP. Nothing to install.
get_current_page_info 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 get_current_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.
Set action: deny in the PolicyLayer policy for get_current_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.
get_current_page_info is provided by the WebScout MCP server (pyscout/webscout-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →