page_go_back

Go back to the previous page in history.

SERVERMcp Anything SOURCEZaymadkid/mcp-anything

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/mcp-anything/page-go-back.md

WHAT IT DOES

What page_go_back does on Mcp Anything

AI agents invoke page_go_back to trigger actions in Mcp Anything. 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.

RISK

Why page_go_back is rated High

This tool triggers a browser navigation action (navigating back in browser history), which is an external operation with side effects that depend on the current browser state. It falls under Execute as it performs a browser action rather than simply reading data or writing/deleting it.

From the tool's definition Go back to the previous page in history

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs page_go_back safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For page_go_back, this is the rule to start with:

page_go_back Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "page_go_back": {
      "limits": [
        {
          "counter": "page_go_back_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every page_go_back call is checked against it from then on.

FAQ

Questions about page_go_back

What does the page_go_back tool do? +

Go back to the previous page in history. It is categorised as a Execute tool in the Mcp Anything MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on page_go_back? +

Register the Mcp Anything MCP server in PolicyLayer and add a rule for page_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 Mcp Anything. Nothing to install.

What risk level is page_go_back? +

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

Can I rate-limit page_go_back? +

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

How do I block page_go_back completely? +

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

What MCP server provides page_go_back? +

page_go_back is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Anything, and thousands of servers like it.

This server

All 261 Mcp Anything tools → High-risk tools on this server →

Across the catalogue

monitor_and_analyze_page on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →