获取指定URL页面的文本内容
AI agents call get_page_text to retrieve information from MCP Browser Text Reader without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool navigates to a URL and retrieves/extracts text content from the page. It performs only data retrieval operations without modifying, deleting, or executing code. The sibling tools (navigate_to_page, get_current_page_text, get_page_info) all indicate passive browser navigation and content extraction. No creation, modification, deletion, execution, or financial operations are involved.
From the tool's definition Tool name 'get_page_text' and description '获取指定URL页面的文本内容' (retrieve text content from specified URL page) indicate retrieval and extraction of data.
Attacks that exploit this kind of access
获取指定URL页面的文本内容. It is categorised as a Read tool in the MCP Browser Text Reader MCP Server, which means it retrieves data without modifying state.
Register the MCP Browser Text Reader 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 MCP Browser Text Reader. 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 MCP Browser Text Reader MCP server (tikous/mymcp). 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 →