browser_navigate_back
Navigate back in the page's history (browser back button). Returns the new URL + title.
This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-navigate-back.md
What browser_navigate_back does on Dialogbrain
AI agents invoke browser_navigate_back to trigger actions in Dialogbrain. 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 |
|---|---|---|---|
page_id | string | Yes |
Parameters from the server's own tool schema.
Why browser_navigate_back is rated High
This tool executes a browser navigation action whose effects depend on the current browsing context and history state. While not destructive or financial, it is an Execute-category tool because it performs an external operation (browser control) rather than merely reading data.
From the tool's definition Tool description states 'Navigate back in the page's history (browser back button)' — this performs an action that triggers external browser behavior and changes application state.
Attacks that exploit this kind of access
The rule that runs browser_navigate_back safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_navigate_back, this is the rule to start with:
browser_navigate_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 Dialogbrain, apply this rule, and every browser_navigate_back call is checked against it from then on.
Questions about browser_navigate_back
Navigate back in the page's history (browser back button). Returns the new URL + title. It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browser_navigate_back accepts 1 parameter: page_id. Required: page_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for browser_navigate_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 Dialogbrain. Nothing to install.
browser_navigate_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 browser_navigate_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 browser_navigate_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.
browser_navigate_back is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue