Get detailed page information including full HTML content, page statistics, and metadata
AI agents call browser_get_page_info to retrieve information from Concurrent Browser MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about a currently-loaded web page (HTML content, statistics, metadata). It performs no state changes, does not execute code or commands, does not delete data, and does not move money. It is a pure read operation that queries page state.
From the tool's definition Tool name 'browser_get_page_info' and description 'Get detailed page information including full HTML content, page statistics, and metadata' indicate data retrieval without modification or execution of external operations.
Documented attack patterns abuse exactly the kind of access browser_get_page_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Concurrent Browser MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_get_page_info:
{
"version": "1",
"default": "deny",
"tools": {
"browser_get_page_info": {}
}
}browser_get_page_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed page information including full HTML content, page statistics, and metadata. It is categorised as a Read tool in the Concurrent Browser MCP MCP Server, which means it retrieves data without modifying state.
Register the Concurrent Browser 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 Concurrent Browser MCP. Nothing to install.
browser_get_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 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.
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.
browser_get_page_info is provided by the Concurrent Browser MCP server (sailaoda/concurrent-browser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Concurrent Browser MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Concurrent Browser MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.