get-page-visible-text
A read tool on the AdsPower LocalAPI MCP server.
This record as markdown: /tools/adspower-adspower-browser/get-page-visible-text.md
What get-page-visible-text does on AdsPower LocalAPI MCP Server
AI agents call get-page-visible-text to retrieve information from AdsPower LocalAPI MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-page-visible-text is rated Low
This tool retrieves rendered page text, which is a non-destructive read operation with minimal blast radius. While it operates within a browser automation context (AdsPower), text extraction itself causes no side effects. Low severity reflects that reading visible text presents minimal risk compared to other operations on this server like close-browser or delete-browser.
From the tool's definition Tool name 'get-page-visible-text' indicates retrieval of text content from a web page without modification. The description is empty, limiting direct confirmation, but the name pattern follows standard read-only operations.
Attacks that exploit this kind of access
The rule that runs get-page-visible-text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdsPower LocalAPI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-page-visible-text, this is the rule to start with:
get-page-visible-text is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdsPower LocalAPI MCP Server, apply this rule, and every get-page-visible-text call is checked against it from then on.
Questions about get-page-visible-text
get-page-visible-text is a read tool on the AdsPower LocalAPI MCP Server MCP server. It is categorised as a Read tool in the AdsPower LocalAPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AdsPower LocalAPI MCP Server MCP server in PolicyLayer and add a rule for get-page-visible-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 AdsPower LocalAPI MCP Server. Nothing to install.
get-page-visible-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-visible-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-visible-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-visible-text is provided by the AdsPower LocalAPI MCP Server MCP server (adspower/adspower-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdsPower LocalAPI MCP Server, and thousands of servers like it.
This server
Across the catalogue