合并工作区工具。action: isolate(隔离工作区)/switch(切换工作区)/merge(合并工作区)/status(工作区状态)。
AI agents use qflow_workspace 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 creates or modifies workspace configuration and state reversibly. While 'merge' could be destructive depending on implementation, the presence of 'isolate', 'switch', and 'status' actions alongside it, combined with typical workspace management semantics, suggests these are configuration changes rather than irreversible deletions.
From the tool's definition Tool performs workspace operations: isolate, switch, merge, and status checks. The merge action modifies workspace state by combining workspaces, which is a reversible data modification. Isolate and switch also alter workspace context/state.
Documented attack patterns abuse exactly the kind of access qflow_workspace 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_workspace:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_workspace": {
"limits": [
{
"counter": "qflow_workspace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_workspace 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: isolate(隔离工作区)/switch(切换工作区)/merge(合并工作区)/status(工作区状态)。. 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_workspace: 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_workspace 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_workspace 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_workspace. 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_workspace 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.