合并评审工具。action: create(创建评审)/comment(添加评论)/resolve(完成评审)/list(列出评审)/get(获取详情)/approve(创建审批)/reject(投票拒绝)/check(检查审批)/readiness(就绪度检查)/analyze(分析工具,需指定type)。
AI agents use qflow_review 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 is a code review and approval management tool. The primary actions are write operations: creating reviews, adding comments, approving, rejecting, and resolving reviews. While it includes read-only actions (list, get, check, analyze), the capability to approve/reject and create/resolve reviews means it modifies project state reversibly.
From the tool's definition The tool description lists actions including 'create(创建评审)' (create review), 'comment(添加评论)' (add comment), 'approve(创建审批)' (create approval), 'reject(投票拒绝)' (vote reject), and 'resolve(完成评审)' (resolve review). These are modifications to review/approval state.
Documented attack patterns abuse exactly the kind of access qflow_review 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_review:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_review": {
"limits": [
{
"counter": "qflow_review_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_review 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(创建评审)/comment(添加评论)/resolve(完成评审)/list(列出评审)/get(获取详情)/approve(创建审批)/reject(投票拒绝)/check(检查审批)/readiness(就绪度检查)/analyze(分析工具,需指定type)。. 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_review: 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_review 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_review 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_review. 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_review 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.