提出 Spec 变更。默认 Delta 格式写入 changes/pending/。full=true 时一站式创建完整 Spec（含 proposal+design+tasks）。
AI agents use qflow_spec_propose 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 project specification data by proposing changes and writing them to a pending directory, or creating complete specifications. These are reversible write operations typical of project management systems where proposals and specs can be edited or discarded. Not destructive since changes are in 'pending' state and appear to be reviewable.
From the tool's definition Tool description states '提出 Spec 变更' (propose Spec changes) and mentions 'Delta 格式写入 changes/pending/' (writes delta format to changes/pending/) and 'full=true 时一站式创建完整 Spec' (creates complete Spec including proposal+design+tasks when full=true).
Documented attack patterns abuse exactly the kind of access qflow_spec_propose 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_spec_propose:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_spec_propose": {
"limits": [
{
"counter": "qflow_spec_propose_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_spec_propose 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.
提出 Spec 变更。默认 Delta 格式写入 changes/pending/。full=true 时一站式创建完整 Spec（含 proposal+design+tasks）。. 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_spec_propose: 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_spec_propose 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_spec_propose 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_spec_propose. 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_spec_propose 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.