chrome_get_page_info

Get current page information (title, URL, DOM elements)

SERVERChrome Feedback SOURCE2019-02-18/mcx

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/2019-02-18-mcx/chrome-get-page-info.md

WHAT IT DOES

What chrome_get_page_info does on Chrome Feedback

AI agents call chrome_get_page_info to retrieve information from Chrome Feedback without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why chrome_get_page_info is rated Low

This tool only retrieves static information about the current page (title, URL, and DOM structure). It performs no write operations, does not execute code, and causes no side effects. It is purely informational, making it a Read category tool with low severity since the data returned is non-sensitive metadata already visible in the browser.

From the tool's definition Tool description states it 'Get[s] current page information (title, URL, DOM elements)' — retrieval of page metadata with no modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs chrome_get_page_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Feedback, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chrome_get_page_info, this is the rule to start with:

chrome_get_page_info Allowed

chrome_get_page_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "chrome_get_page_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Feedback, apply this rule, and every chrome_get_page_info call is checked against it from then on.

FAQ

Questions about chrome_get_page_info

What does the chrome_get_page_info tool do? +

Get current page information (title, URL, DOM elements). It is categorised as a Read tool in the Chrome Feedback MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on chrome_get_page_info? +

Register the Chrome Feedback MCP server in PolicyLayer and add a rule for chrome_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 Chrome Feedback. Nothing to install.

What risk level is chrome_get_page_info? +

chrome_get_page_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit chrome_get_page_info? +

Yes. Add a rate_limit block to the chrome_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.

How do I block chrome_get_page_info completely? +

Set action: deny in the PolicyLayer policy for chrome_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.

What MCP server provides chrome_get_page_info? +

chrome_get_page_info is provided by the Chrome Feedback MCP server (2019-02-18/mcx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Feedback, and thousands of servers like it.

This server

All 16 Chrome Feedback tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →