Lists all open tabs in the browser with their URLs and titles.
AI agents call list_pages to retrieve information from Auth Fetch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation—it only retrieves and queries the state of open browser tabs. However, the severity is elevated to medium rather than low because: (1) the list could reveal sensitive URLs the user is accessing in their authenticated sessions, (2) when combined with sibling tools like auth_fetch, it exposes information about what pages are available in the user's authenticated context, and (3) an AI agent…
From the tool's definition Tool name 'list_pages' and description 'Lists all open tabs in the browser with their URLs and titles' indicate data retrieval with no modification or execution.
Documented attack patterns abuse exactly the kind of access list_pages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Auth Fetch, and nothing reaches the server without passing your rules. This is the rule we recommend for list_pages:
{
"version": "1",
"default": "deny",
"tools": {
"list_pages": {}
}
}list_pages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists all open tabs in the browser with their URLs and titles. It is categorised as a Read tool in the Auth Fetch MCP Server, which means it retrieves data without modifying state.
Register the Auth Fetch MCP server in PolicyLayer and add a rule for list_pages: 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 Auth Fetch. Nothing to install.
list_pages 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 list_pages 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 list_pages. 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.
list_pages is provided by the Auth Fetch MCP server (ymw0407/auth-fetch-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Auth Fetch tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Auth Fetch tools catalogued and risk-classified — across an index of 42,500+ MCP servers.