Get semantic information about the current page, including interactive elements, their indices, and all the text content on the page. Returns a diff from one of the previous calls if available and if the diff is smaller than the full content. If you
AI agents call getPageInfo to retrieve information from Chrome MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
getPageInfo retrieves and queries page data (interactive elements, indices, text content) without creating, modifying, deleting, or executing anything. It has no side effects beyond information gathering. This is a pure Read operation with minimal security risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Get[s] semantic information about the current page' and 'Returns a diff from one of the previous calls if available'. The verb 'Get' and absence of any mutation, deletion, or execution language indicates a retrieval-only operation.
Documented attack patterns abuse exactly the kind of access getPageInfo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getPageInfo:
{
"version": "1",
"default": "deny",
"tools": {
"getPageInfo": {}
}
}getPageInfo 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 semantic information about the current page, including interactive elements, their indices, and all the text content on the page. Returns a diff from one of the previous calls if available and if the diff is smaller than the full content. If you. It is categorised as a Read tool in the Chrome MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chrome MCP Server MCP server in PolicyLayer and add a rule for getPageInfo: 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 Chrome MCP Server. Nothing to install.
getPageInfo 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 getPageInfo 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 getPageInfo. 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.
getPageInfo is provided by the Chrome MCP Server MCP server (lxe/chrome-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Chrome MCP Server, 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.
11 Chrome MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.