wait_for_navigation · InSite MCP: Risk & Policy

WHAT IT DOES

What wait_for_navigation does on InSite

AI agents invoke wait_for_navigation 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 wait_for_navigation needs a policy

This tool executes a browser operation (navigation waiting) that can have side effects depending on context—the page navigated to could trigger external requests, load different content, or execute scripts on the new page. While not directly destructive or financial, it's an active operation that changes browser state and could be misused to navigate to malicious sites or trigger unintended server requests.

From the tool's definition Tool name 'wait_for_navigation' and description 'Wait for page navigation to complete' indicate it triggers or monitors browser navigation actions. As part of a browser automation suite, it controls page state transitions and navigation flow.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait_for_navigation Rate-limited

wait_for_navigation 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": {
    "wait_for_navigation": {
      "limits": [
        {
          "counter": "wait_for_navigation_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 wait_for_navigation

What does the wait_for_navigation tool do? +

Wait for page navigation to complete. 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 wait_for_navigation? +

Register the InSite MCP server in PolicyLayer and add a rule for wait_for_navigation: 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 wait_for_navigation? +

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

Can I rate-limit wait_for_navigation? +

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

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

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