New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

browser_go_forward

A execute tool on the Looking Glass MCP server.

SERVERLooking Glass SOURCElooking-glass-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-go-forward.md

What browser_go_forward does on Looking Glass

AI agents invoke browser_go_forward to trigger actions in Looking Glass. 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.

Why browser_go_forward is rated High

Browser navigation actions are external operations that change the browser state. 'Go forward' navigates to the next page in history, which is an Execute-level action. Severity is medium as it could cause unintended navigation to pages with side effects, but is generally reversible.

From the tool's definition Tool name 'browser_go_forward' implies triggering a browser navigation action (moving forward in browser history). Description is empty and uninformative, lowering confidence.

Questions about browser_go_forward

What does the browser_go_forward tool do? +

browser_go_forward is a execute tool on the Looking Glass MCP server. It is categorised as a Execute tool in the Looking Glass MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_go_forward? +

Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_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 Looking Glass. Nothing to install.

What risk level is browser_go_forward? +

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

Can I rate-limit browser_go_forward? +

Yes. Add a rate_limit block to the browser_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.

How do I block browser_go_forward completely? +

Set action: deny in the PolicyLayer policy for browser_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.

What MCP server provides browser_go_forward? +

browser_go_forward is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Looking Glass, 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 Looking Glass'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.