全系统健康检查：status=完整诊断，drift=配置漂移检测，watch_start=启动文件监控，watch_stop=停止监控，watch_events=获取监控事件。
AI agents call qflow_diagnostics 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 performs system health checks, configuration drift detection, and file monitoring — all of which are fundamentally read/observe operations. The watch_start/watch_stop sub-commands start and stop monitoring agents but do not modify application data or execute destructive actions.
From the tool's definition 健康检查 (health check), 配置漂移检测 (configuration drift detection), 获取监控事件 (get monitoring events) — all operations are diagnostic/read in nature
Documented attack patterns abuse exactly the kind of access qflow_diagnostics 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_diagnostics:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_diagnostics": {}
}
}qflow_diagnostics 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.
全系统健康检查：status=完整诊断，drift=配置漂移检测，watch_start=启动文件监控，watch_stop=停止监控，watch_events=获取监控事件。. 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_diagnostics: 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_diagnostics 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_diagnostics 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_diagnostics. 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_diagnostics 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.