navigate_to_states · Qontinui MCP Server MCP: Risk & Policy

WHAT IT DOES

What navigate_to_states does on Qontinui MCP Server

AI agents invoke navigate_to_states to trigger actions in Qontinui MCP Server. 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_to_states needs a policy

Navigation via pathfinding is an Execute-class action because it triggers workflow state transitions and interactive automation whose effects depend on arguments (target states). While not inherently destructive or financial, it modifies the state of automated systems and UI interactions, creating external side effects.

From the tool's definition Tool performs 'navigate to target states using pathfinding' which is an active operation that triggers visual automation workflows to move between UI states.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

navigate_to_states Rate-limited

navigate_to_states 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_to_states": {
      "limits": [
        {
          "counter": "navigate_to_states_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 Qontinui MCP Server, so you can run agents against it safely.

FAQ

Questions about navigate_to_states

What does the navigate_to_states tool do? +

Navigate to target states using pathfinding. It is categorised as a Execute tool in the Qontinui MCP Server 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_to_states? +

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

What risk level is navigate_to_states? +

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

Can I rate-limit navigate_to_states? +

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

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

navigate_to_states is provided by the Qontinui MCP Server MCP server (qontinui/qontinui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.