从 Spec 生成实现计划（技术方案+数据模型+API契约+快速启动）
AI agents use qflow_plan_generate 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 generates and creates multiple planning artifacts (技术方案=technical solution, 数据模型=data model, API契约=API contract, 快速启动=quick start). Generation of planning documents constitutes creating new data/content.
From the tool's definition Tool name contains 'generate' and description states it creates implementation plans including technical solutions, data models, API contracts, and quick start guides. These are artifacts that are created/written rather than merely retrieved.
Documented attack patterns abuse exactly the kind of access qflow_plan_generate 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_plan_generate:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_plan_generate": {
"limits": [
{
"counter": "qflow_plan_generate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_plan_generate 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.
从 Spec 生成实现计划（技术方案+数据模型+API契约+快速启动）. 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_plan_generate: 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_plan_generate 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_plan_generate 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_plan_generate. 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_plan_generate 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.