read_page_content
Read the HTML source of a Safari tab. Specify window and tab index from list_tabs.
This record as markdown: /tools/io-github-heznpc-iconnect/read-page-content.md
What read_page_content does on Iconnect
AI agents call read_page_content to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why read_page_content is rated Low
This tool queries and retrieves data (HTML source code) from an already-open Safari tab. It performs no side effects, creates no modifications, executes no code, deletes nothing, and moves no money. It is a straightforward read operation on existing browser state, classified as 'Read' with low severity since it only accesses content the user's own Safari session already has open.
From the tool's definition Tool name is 'read_page_content' and description explicitly states 'Read the HTML source of a Safari tab'. The verb 'read' and action of retrieving HTML content with no modification capability confirms this is a retrieval operation.
Attacks that exploit this kind of access
The rule that runs read_page_content safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_page_content, this is the rule to start with:
read_page_content 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 Iconnect, apply this rule, and every read_page_content call is checked against it from then on.
Questions about read_page_content
Read the HTML source of a Safari tab. Specify window and tab index from list_tabs. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for read_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 Iconnect. Nothing to install.
read_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 read_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 read_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.
read_page_content is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue