合并治理原则工具。action: init(初始化)/get(获取列表)/set(添加原则)/validate(验证内容)。
AI agents use qflow_constitution 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 'set' action creates or modifies governance principles, making this a Write operation. While 'get' and 'validate' are read-like operations, 'set' and 'init' can alter the configuration state of the system. The tool manages governance rules which could affect project behavior if misconfigured by an AI agent, warranting medium severity.
From the tool's definition Tool provides actions: init (initialize), get (list), set (add principles), validate (verify content). The 'set' action explicitly adds/modifies governance principles; 'init' initializes state; 'validate' checks content.
Documented attack patterns abuse exactly the kind of access qflow_constitution 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_constitution:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_constitution": {
"limits": [
{
"counter": "qflow_constitution_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_constitution 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: init(初始化)/get(获取列表)/set(添加原则)/validate(验证内容)。. 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_constitution: 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_constitution 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_constitution 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_constitution. 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_constitution 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.