Get the history of visited URLs, most recent urls first
AI agents call puppeteer_page_history to retrieve information from Puppeteer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves browsing history data without creating, modifying, executing, or deleting anything. It is purely informational and has minimal security impact even if misused by an agent — the worst case is leaking what URLs were visited in the current session, which does not affect external systems or cause destructive changes.
From the tool's definition Tool description states 'Get the history of visited URLs' — a retrieval operation with no modification or execution side effects. The verb 'Get' and context of reading historical data confirms read-only behavior.
Attacks that exploit this kind of access
Get the history of visited URLs, most recent urls first. It is categorised as a Read tool in the Puppeteer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Puppeteer MCP Server MCP server in PolicyLayer and add a rule for puppeteer_page_history: 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 Puppeteer MCP Server. Nothing to install.
puppeteer_page_history 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 puppeteer_page_history 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 puppeteer_page_history. 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.
puppeteer_page_history is provided by the Puppeteer MCP Server MCP server (jwaldor/mcp-scrape-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →