chrome_go_back
Navigates the current Google Chrome tab back to the previous page.
This record as markdown: /tools/com-local-mcp-local-mcp/chrome-go-back.md
What chrome_go_back does on Local
AI agents invoke chrome_go_back to trigger actions in Local. 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 |
|---|---|---|---|
window_index | integer | — |
Parameters from the server's own tool schema.
Why chrome_go_back is rated High
This tool triggers a browser navigation action (going back in history), which is an external browser operation with side effects beyond simple data retrieval. It falls under Execute as it controls browser behavior, though the blast radius is low since it only moves back in browsing history.
From the tool's definition Navigates the current Google Chrome tab back to the previous page
Attacks that exploit this kind of access
The rule that runs chrome_go_back safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chrome_go_back, this is the rule to start with:
chrome_go_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 Local, apply this rule, and every chrome_go_back call is checked against it from then on.
Questions about chrome_go_back
Navigates the current Google Chrome tab back to the previous page. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
chrome_go_back accepts 1 parameter: window_index. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for chrome_go_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 Local. Nothing to install.
chrome_go_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 chrome_go_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 chrome_go_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.
chrome_go_back is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
Across the catalogue