scan_page

Read the current page as simplified HTML/text, preserving login state from the real browser.

SERVERAgent Browser SOURCE335234131/agent-browser-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/335234131-agent-browser-mcp/scan-page.md

WHAT IT DOES

What scan_page does on Agent Browser

AI agents call scan_page to retrieve information from Agent Browser without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why scan_page is rated Low

scan_page retrieves and parses page content without side effects, making it a Read operation. However, severity is elevated to 'high' because it operates within a real Chrome browser with 'login sessions, cookies, and open tabs' intact.

From the tool's definition Tool description explicitly states 'Read the current page as simplified HTML/text' and name 'scan_page' indicates information retrieval. No modification, deletion, or execution of code is performed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scan_page safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Browser, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scan_page, this is the rule to start with:

scan_page Allowed

scan_page is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scan_page": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agent Browser, apply this rule, and every scan_page call is checked against it from then on.

FAQ

Questions about scan_page

What does the scan_page tool do? +

Read the current page as simplified HTML/text, preserving login state from the real browser. It is categorised as a Read tool in the Agent Browser MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on scan_page? +

Register the Agent Browser MCP server in PolicyLayer and add a rule for scan_page: 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 Agent Browser. Nothing to install.

What risk level is scan_page? +

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

Can I rate-limit scan_page? +

Yes. Add a rate_limit block to the scan_page 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 scan_page completely? +

Set action: deny in the PolicyLayer policy for scan_page. 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 scan_page? +

scan_page is provided by the Agent Browser MCP server (335234131/agent-browser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agent Browser, and thousands of servers like it.

This server

All 20 Agent Browser tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →