设置任务状态。当设为 done 时自动：解除阻塞的下游任务、推荐下一任务。返回更新结果和推荐的下一任务。
AI agents use qflow_task_set_status 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 modifies task state within a project management system. While it changes data (task status), the operation is reversible—a task status can be changed again. The tool does not delete data permanently or execute arbitrary code. The side effects (unblocking dependent tasks, recommendations) are deterministic outcomes of the status change operation.
From the tool's definition Tool description indicates it 'sets task status' (设置任务状态) and when set to 'done' it performs actions including 'unblocking downstream tasks' (解除阻塞的下游任务) and 'recommending next task' (推荐下一任务). These are state modifications to task management data.
Documented attack patterns abuse exactly the kind of access qflow_task_set_status 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_set_status:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_task_set_status": {
"limits": [
{
"counter": "qflow_task_set_status_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_task_set_status 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.
设置任务状态。当设为 done 时自动：解除阻塞的下游任务、推荐下一任务。返回更新结果和推荐的下一任务。. 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_task_set_status: 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_set_status 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_task_set_status 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_set_status. 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_set_status 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.