Navigate forward in browser history
AI agents invoke puppeteer_go_forward to trigger actions in Claude TypeScript MCP Servers. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool controls browser navigation by moving forward in browser history, which is an external browser action. It triggers real browser operations that can load pages, execute scripts on those pages, and interact with web content. While it seems benign, browser actions are classified as Execute since effects depend on what page gets loaded.
From the tool's definition Navigate forward in browser history
Documented attack patterns abuse exactly the kind of access puppeteer_go_forward gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude TypeScript MCP Servers, and nothing reaches the server without passing your rules. This is the rule we recommend for puppeteer_go_forward:
{
"version": "1",
"default": "deny",
"tools": {
"puppeteer_go_forward": {
"limits": [
{
"counter": "puppeteer_go_forward_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} puppeteer_go_forward stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Navigate forward in browser history. It is categorised as a Execute tool in the Claude TypeScript MCP Servers MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude TypeScript MCP Servers MCP server in PolicyLayer and add a rule for puppeteer_go_forward: 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 Claude TypeScript MCP Servers. Nothing to install.
puppeteer_go_forward is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the puppeteer_go_forward 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_go_forward. 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_go_forward is provided by the Claude TypeScript MCP Servers MCP server (ukkz/claude-ts-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude TypeScript MCP Servers, 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.
84 Claude TypeScript MCP Servers tools catalogued and risk-classified — across an index of 43,000+ MCP servers.