Extract raw text content from the page, prioritizing article content. Ideal for reading articles, blog posts, or other text-heavy pages. Returns plain text without HTML formatting.
AI agents call get_page_text to retrieve information from OpenChrome without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and extracts existing page content without modifying state, executing code, or causing side effects. It is a pure read operation that queries the DOM/rendered page content. No reversible or irreversible changes are made to the browser, page, or external systems. The output is plain text suitable for AI consumption, with no capability to alter data or trigger external operations.
From the tool's definition Tool name 'get_page_text' and description 'Extract raw text content from the page' with 'Returns plain text without HTML formatting' indicate retrieval only.
Documented attack patterns abuse exactly the kind of access get_page_text gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenChrome, and nothing reaches the server without passing your rules. This is the rule we recommend for get_page_text:
{
"version": "1",
"default": "deny",
"tools": {
"get_page_text": {}
}
}get_page_text 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.
Extract raw text content from the page, prioritizing article content. Ideal for reading articles, blog posts, or other text-heavy pages. Returns plain text without HTML formatting. It is categorised as a Read tool in the OpenChrome MCP Server, which means it retrieves data without modifying state.
Register the OpenChrome MCP server in PolicyLayer and add a rule for get_page_text: 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 OpenChrome. Nothing to install.
get_page_text 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_text 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_text. 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_text is provided by the OpenChrome MCP server (shaun0927/openchrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 106 OpenChrome tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
106 OpenChrome tools catalogued and risk-classified — across an index of 42,500+ MCP servers.