从代码库生成 Spec。默认分析文件提取架构信息，structured=true 时 AI 生成结构化 Spec（含用户故事和验收条件）。
AI agents call qflow_spec_generate 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.
This tool reads and analyzes the codebase to generate a specification document. It extracts architectural information and optionally generates structured specs with user stories and acceptance criteria. The primary action is reading/analyzing existing code files and producing output — no data is modified, deleted, or executed. The severity is low because misuse would at most produce inaccurate documentation.
From the tool's definition 从代码库生成 Spec。默认分析文件提取架构信息 (analyzes files to extract architecture information, generates spec from codebase)
Documented attack patterns abuse exactly the kind of access qflow_spec_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_spec_generate:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_spec_generate": {}
}
}qflow_spec_generate 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.
从代码库生成 Spec。默认分析文件提取架构信息，structured=true 时 AI 生成结构化 Spec（含用户故事和验收条件）。. 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_spec_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_spec_generate 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_spec_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_spec_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_spec_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.