项目状态感知智能导航。自动检测项目阶段（init/planning/implementing/reviewing/done），推荐下一步操作。
AI agents call qflow_what_next to retrieve information from Qflow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool detects the current project phase and recommends next actions. This is fundamentally a read/query operation — it reads project state and surfaces guidance. No evidence of writing, executing, or destructive operations. Confidence is moderate because the description is brief and in Chinese, leaving some ambiguity about whether 'recommending' triggers any side effects.
From the tool's definition 项目状态感知智能导航。自动检测项目阶段（init/planning/implementing/reviewing/done），推荐下一步操作。
Documented attack patterns abuse exactly the kind of access qflow_what_next 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_what_next:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_what_next": {}
}
}qflow_what_next is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
项目状态感知智能导航。自动检测项目阶段（init/planning/implementing/reviewing/done），推荐下一步操作。. It is categorised as a Read tool in the Qflow MCP Server, which means it retrieves data without modifying state.
Register the Qflow MCP server in PolicyLayer and add a rule for qflow_what_next: 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_what_next is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the qflow_what_next 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_what_next. 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_what_next 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.