按 ID 获取任务详情，包含所有字段（标题、描述、状态、优先级、依赖、标签、子任务、元数据等）。
AI agents call qflow_task_get 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.
This tool retrieves task information by ID and returns fields like title, description, status, priority, dependencies, labels, subtasks, and metadata. It is a read-only query operation with no side effects, data modification, or destructive actions. The severity is low because retrieving existing task metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'qflow_task_get' and description '按 ID 获取任务详情，包含所有字段（标题、描述、状态、优先级、依赖、标签、子任务、元数据等）' indicates retrieval of task details by ID with no modification.
Documented attack patterns abuse exactly the kind of access qflow_task_get 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_task_get:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_task_get": {}
}
}qflow_task_get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
按 ID 获取任务详情，包含所有字段（标题、描述、状态、优先级、依赖、标签、子任务、元数据等）。. It is categorised as a Read tool in the Qflow MCP Server, which means it retrieves data without modifying state.
Register the Qflow MCP server in PolicyLayer and add a rule for qflow_task_get: 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_task_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the qflow_task_get 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_task_get. 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_task_get 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.