按需加载 CLAUDE.md 上下文模块。可用模块：core, phase1, phase2, ui-constraints, context-guard, thinking-tiers, iron-rules, readme-spec, reverse。返回模块内容和 token 消耗。
AI agents call qflow_context_load 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 is a read-only operation that loads predefined context modules and returns their content. It has no side effects, does not modify any data, does not execute code or commands, does not delete anything, and involves no financial transactions. The blast radius of misuse is minimal—an agent could retrieve unnecessary context modules and consume tokens, but cannot damage systems or data.
From the tool's definition Tool name and description indicate it 'loads' (加载) context modules on demand and 'returns module content and token consumption' (返回模块内容和token消耗). No creation, modification, deletion, code execution, or financial operations are described.
Documented attack patterns abuse exactly the kind of access qflow_context_load 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_context_load:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_context_load": {}
}
}qflow_context_load 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.
按需加载 CLAUDE.md 上下文模块。可用模块：core, phase1, phase2, ui-constraints, context-guard, thinking-tiers, iron-rules, readme-spec, reverse。返回模块内容和 token 消耗。. 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_context_load: 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_context_load 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_context_load 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_context_load. 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_context_load 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.