Read the content and metadata of the current page (see browser_docs)
AI agents call browser_read_page to retrieve information from Browser MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves page content and metadata without modifying, executing, or deleting anything. It is a pure read operation with minimal risk—the only potential concern would be accessing sensitive data already loaded in the browser, but that is not a misuse of the tool itself. Low severity reflects limited blast radius if misused by an agent.
From the tool's definition Tool name is 'browser_read_page' and description states 'Read the content and metadata of the current page'. The verb 'read' and explicit statement of reading content/metadata indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Read the content and metadata of the current page (see browser_docs). It is categorised as a Read tool in the Browser MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browser MCP Server MCP server in PolicyLayer and add a rule for browser_read_page: 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 Browser MCP Server. Nothing to install.
browser_read_page 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_read_page 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_read_page. 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_read_page is provided by the Browser MCP Server MCP server (madebytokens/browser-mcp-server). 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 →