Get the full content and metadata of a web page. Returns text content by default for optimal performance.
AI agents call get_page_content to retrieve information from Browser MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns page data without modifying, executing code, deleting content, or triggering external operations. It is a passive information-gathering operation analogous to fetching or retrieving data. The broader server context includes execute capabilities (execute_javascript), but this specific tool performs only content retrieval, placing it firmly in the Read category with low severity.
From the tool's definition Tool name 'get_page_content' and description state it retrieves 'full content and metadata of a web page' with 'text content by default' — a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the full content and metadata of a web page. Returns text content by default for optimal performance. It is categorised as a Read tool in the Browser MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the Browser MCP Bridge MCP server in PolicyLayer and add a rule for get_page_content: 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 Bridge. Nothing to install.
get_page_content 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_page_content 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_page_content. 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_page_content is provided by the Browser MCP Bridge MCP server (robhicks/browser-mcp-bridge). 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 →