browse_back
Navigate the session back one page (browser history). Re-snapshot after — @eN refs regenerate per page.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/browse-back.md
What browse_back does on Gateway
AI agents invoke browse_back to trigger actions in Gateway. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
browser_id | string | Yes | from browse_open |
Parameters from the server's own tool schema.
Why browse_back is rated High
This tool triggers a browser navigation action (going back in history) and captures a new snapshot, constituting an external browser operation with session state effects. It fits Execute as it drives browser actions whose effects depend on the current session state.
From the tool's definition Navigate the session back one page (browser history). Re-snapshot after
Attacks that exploit this kind of access
The rule that runs browse_back safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browse_back, this is the rule to start with:
browse_back 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every browse_back call is checked against it from then on.
Questions about browse_back
Navigate the session back one page (browser history). Re-snapshot after — @eN refs regenerate per page. It is categorised as a Execute tool in the Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browse_back accepts 1 parameter: browser_id. Required: browser_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for browse_back: 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 Gateway. Nothing to install.
browse_back 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 browse_back 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 browse_back. 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.
browse_back is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
Across the catalogue