切换到指定的工作区标签。每个标签对应独立的任务文件，实现任务隔离。
AI agents use qflow_use_tag 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 the active workspace context by switching to a different tag, which affects which task file is in use. While not destructive (no data is deleted) and not a pure read operation (it changes application state), it constitutes a Write action as it alters the working context.
From the tool's definition Tool description states '切换到指定的工作区标签' (switch to specified workspace tag) where 'each tag corresponds to independent task files, implementing task isolation.' The action of switching/selecting a tag implies modification of state or context that persists…
Documented attack patterns abuse exactly the kind of access qflow_use_tag 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_use_tag:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_use_tag": {
"limits": [
{
"counter": "qflow_use_tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_use_tag 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.
切换到指定的工作区标签。每个标签对应独立的任务文件，实现任务隔离。. 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_use_tag: 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_use_tag 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_use_tag 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_use_tag. 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_use_tag 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.