合并 Sprint 工具。action: create(创建)/get(获取详情)/add_story(添加故事)/update_story(更新故事状态)/complete(结束Sprint)。
AI agents use qflow_sprint 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.
The tool creates and modifies sprint data (stories, status) but does not delete or irreversibly destroy data. The 'complete' action ends a sprint but does not purge it. These are reversible write operations typical of project management systems. While 'get' is read-only, the presence of multiple write operations (create, add, update) makes Write the primary category.
From the tool's definition Tool description specifies actions: create (创建), get (获取详情), add_story (添加故事), update_story (更新故事状态), and complete (结束Sprint). The create, add_story, and update_story operations modify project management data reversibly.
Documented attack patterns abuse exactly the kind of access qflow_sprint 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_sprint:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_sprint": {
"limits": [
{
"counter": "qflow_sprint_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_sprint 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.
合并 Sprint 工具。action: create(创建)/get(获取详情)/add_story(添加故事)/update_story(更新故事状态)/complete(结束Sprint)。. 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_sprint: 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_sprint 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_sprint 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_sprint. 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_sprint 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.