项目报告：progress=进度报告（含状态统计、标签分组、阻塞分析），complexity=复杂度报告（含评分分布、高复杂度任务、拆解建议）
AI agents call qflow_report 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 generates project reports (progress and complexity) by reading and aggregating existing project data. It retrieves status statistics, tag groupings, blocking analysis, score distributions, and decomposition suggestions. No data is created, modified, or deleted — it is purely a read/query operation.
From the tool's definition 项目报告：progress=进度报告（含状态统计、标签分组、阻塞分析），complexity=复杂度报告（含评分分布、高复杂度任务、拆解建议）
Documented attack patterns abuse exactly the kind of access qflow_report 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_report:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_report": {}
}
}qflow_report 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.
项目报告：progress=进度报告（含状态统计、标签分组、阻塞分析），complexity=复杂度报告（含评分分布、高复杂度任务、拆解建议）. 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_report: 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_report 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_report 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_report. 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_report 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.