合并模板工具。action: create(创建模板)/apply(应用模板)/list(列出模板)。
AI agents use qflow_template 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 enables creation and application of templates, which are reversible write operations that generate or modify project artifacts. While 'list' is read-only, the tool's focus on 'create' and 'apply' makes it primarily a Write category tool. No permanent deletion or code execution is evident, and no financial impact.
From the tool's definition Tool description specifies actions: create(创建模板)/apply(应用模板)/list(列出模板). The 'create' and 'apply' actions modify or create template artifacts; 'list' is read-only but the tool's primary purpose includes state-changing operations.
Documented attack patterns abuse exactly the kind of access qflow_template 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_template:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_template": {
"limits": [
{
"counter": "qflow_template_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_template 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.
合并模板工具。action: create(创建模板)/apply(应用模板)/list(列出模板)。. 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_template: 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_template 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_template 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_template. 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_template 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.