作用域导航：up=子任务提升为顶层任务, down=顶层任务降级为子任务, adjust=动态调节任务范围
AI agents use qflow_scope_navigate to create or update resources in Qflow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qflow environment.
This tool modifies the hierarchical structure and scope of tasks — promoting, demoting, and adjusting them. These are reversible structural changes to task organization, fitting the Write category. No code execution or irreversible deletion is implied. Severity is medium because misuse could disorganize project structure significantly.
From the tool's definition up=子任务提升为顶层任务, down=顶层任务降级为子任务, adjust=动态调节任务范围 (promotes subtasks to top-level, demotes top-level tasks to subtasks, dynamically adjusts task scope)
Documented attack patterns abuse exactly the kind of access qflow_scope_navigate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qflow, and nothing reaches the server without passing your rules. This is the rule we recommend for qflow_scope_navigate:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_scope_navigate": {
"limits": [
{
"counter": "qflow_scope_navigate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_scope_navigate stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
作用域导航：up=子任务提升为顶层任务, down=顶层任务降级为子任务, adjust=动态调节任务范围. It is categorised as a Write tool in the Qflow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Qflow MCP server in PolicyLayer and add a rule for qflow_scope_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 Qflow. Nothing to install.
qflow_scope_navigate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the qflow_scope_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.
Set action: deny in the PolicyLayer policy for qflow_scope_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.
qflow_scope_navigate is provided by the Qflow MCP server (pangu-immortal/qflow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Qflow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
50 Qflow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.