navigate · QA Agent Pro MCP: Risk & Policy

WHAT IT DOES

What navigate does on QA Agent Pro

AI agents invoke navigate to trigger actions in QA Agent Pro. 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 navigate needs a policy

Navigation is an Execute-category action because it triggers an external operation (browser request/page load) with side effects that depend entirely on the argument supplied. While the action itself is reversible and does not delete or modify data, it causes the browser to fetch and load remote resources, which qualifies as triggering an external operation.

From the tool's definition Tool description states 'Navigate to a specific URL in the browser' — this is an action that controls external behavior (browser navigation) whose effects depend on the URL argument provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

navigate Rate-limited

navigate 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": {
    "navigate": {
      "limits": [
        {
          "counter": "navigate_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 QA Agent Pro, so you can run agents against it safely.

FAQ

Questions about navigate

What does the navigate tool do? +

Navigate to a specific URL in the browser. It is categorised as a Execute tool in the QA Agent Pro MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on navigate? +

Register the QA Agent Pro MCP server in PolicyLayer and add a rule for navigate: 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 QA Agent Pro. Nothing to install.

What risk level is navigate? +

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

Can I rate-limit navigate? +

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

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

navigate is provided by the QA Agent Pro MCP server (samusilv/qa-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.