AI agents call qflow_task_tree 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 retrieves (reads) a hierarchical tree of tasks and their subtasks recursively. It is a pure read/query operation with no side effects. Misuse potential is low as it only exposes task structure data.
From the tool's definition 递归获取任务及其所有子任务的树结构 — '获取' means 'retrieve/get', describing recursive retrieval of task and subtask tree structure
Documented attack patterns abuse exactly the kind of access qflow_task_tree 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_task_tree:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_task_tree": {}
}
}qflow_task_tree 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.
递归获取任务及其所有子任务的树结构. 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_task_tree: 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_task_tree 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_task_tree 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_task_tree. 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_task_tree 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.