go_back · InSite MCP: Risk & Policy

WHAT IT DOES

What go_back does on InSite

AI agents invoke go_back to trigger actions in InSite. 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 IT NEEDS A POLICY

Why go_back needs a policy

This tool triggers a browser navigation action, changing the browser's state by moving back in history. It's an external browser operation whose effects depend on the current navigation context, fitting the Execute category. Misuse could disrupt automated workflows or navigate away from critical pages mid-task.

From the tool's definition Navigate back in browser history

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

go_back Rate-limited

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": {
    "go_back": {
      "limits": [
        {
          "counter": "go_back_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches InSite, so you can run agents against it safely.

FAQ

Questions about go_back

What does the go_back tool do? +

Navigate back in browser history. It is categorised as a Execute tool in the InSite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on go_back? +

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

What risk level is go_back? +

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

Can I rate-limit go_back? +

Yes. Add a rate_limit block to the 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 go_back completely? +

Set action: deny in the PolicyLayer policy for 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 go_back? +

go_back is provided by the InSite MCP server (jowharshamshiri/insite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.