Low Risk

qflow_clarification

需求澄清管理:ask=提出澄清问题,answer=回答问题,list=列出问题,unanswered=获取未回答问题

How to control qflow_clarification ↓

What qflow_clarification does on Qflow

AI agents call qflow_clarification to retrieve information from Qflow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why qflow_clarification needs a policy

The qflow_clarification tool is a requirement management utility that facilitates asking, answering, listing, and retrieving clarification questions within a project context. These are fundamentally read operations that query or retrieve clarification data.

From the tool's definition Tool operations are: ask=提出澄清问题 (ask clarification question), answer=回答问题 (answer question), list=列出问题 (list questions), unanswered=获取未回答问题 (get unanswered questions).

Documented attack patterns abuse exactly the kind of access qflow_clarification gives an agent:

How to control qflow_clarification

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_clarification:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "qflow_clarification": {}
  }
}

qflow_clarification is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Qflow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about qflow_clarification

What does the qflow_clarification tool do? +

需求澄清管理:ask=提出澄清问题,answer=回答问题,list=列出问题,unanswered=获取未回答问题. It is categorised as a Read tool in the Qflow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on qflow_clarification? +

Register the Qflow MCP server in PolicyLayer and add a rule for qflow_clarification: 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.

What risk level is qflow_clarification? +

qflow_clarification is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit qflow_clarification? +

Yes. Add a rate_limit block to the qflow_clarification 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.

How do I block qflow_clarification completely? +

Set action: deny in the PolicyLayer policy for qflow_clarification. 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.

What MCP server provides qflow_clarification? +

qflow_clarification 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.

Enforce policy on every Qflow tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.