Low Risk

get_page_text

Get all visible text from the current browser page. Faster than OCR for web content.

How to control get_page_text ↓

What get_page_text does on Macos Control

AI agents call get_page_text to retrieve information from Macos Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_page_text needs a policy

This tool retrieves and queries visible text content from a webpage without creating, modifying, deleting, or executing any operations. It is a passive data retrieval function with no side effects, making it a Read category tool with low severity risk.

From the tool's definition Tool description states 'Get all visible text from the current browser page' with no modification, deletion, or execution capabilities mentioned.

Documented attack patterns abuse exactly the kind of access get_page_text gives an agent:

How to control get_page_text

PolicyLayer is an MCP gateway — it sits between your AI agents and Macos Control, and nothing reaches the server without passing your rules. This is the rule we recommend for get_page_text:

policy.json
{
  "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.

  1. Create a free account and register Macos Control — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_page_text

What does the get_page_text tool do? +

Get all visible text from the current browser page. Faster than OCR for web content. It is categorised as a Read tool in the Macos Control MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_page_text? +

Register the Macos Control 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 Macos Control. Nothing to install.

What risk level is get_page_text? +

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

Can I rate-limit get_page_text? +

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.

How do I block get_page_text completely? +

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.

What MCP server provides get_page_text? +

get_page_text is provided by the Macos Control MCP server (peterhdd/macos-control-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Macos Control tool call.

Start from Macos Control, 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.

22 Macos Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.