AI agents call get_page_content to retrieve information from Chrome Debug 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 and queries the current page's HTML structure. It performs no modifications, deletions, or external operations—purely extracting information for inspection. While used in a browser automation context with other tools capable of clicks and navigation, this specific tool itself is read-only.
From the tool's definition Tool name 'get_page_content' and description '获取当前页面的HTML内容' (retrieve current page HTML content) indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_page_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome Debug MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_page_content:
{
"version": "1",
"default": "deny",
"tools": {
"get_page_content": {}
}
}get_page_content 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.
获取当前页面的HTML内容. It is categorised as a Read tool in the Chrome Debug MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chrome Debug MCP Server 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 Chrome Debug MCP Server. 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 Chrome Debug MCP Server MCP server (rainmen-xia/chrome-debug-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Chrome Debug 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.
10 Chrome Debug MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.