browser_navigate_back

Navigate back in the page's history (browser back button). Returns the new URL + title.

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp
High RISK CLASS
Category Execute
Parameters 11 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about browser_navigate_back

What does the browser_navigate_back tool do? +

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.

What parameters does browser_navigate_back accept? +

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.

How do I enforce a policy on browser_navigate_back? +

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.

What risk level is browser_navigate_back? +

browser_navigate_back is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_navigate_back? +

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.

How do I block browser_navigate_back completely? +

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.

What MCP server provides browser_navigate_back? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Dialogbrain's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.