压缩上下文，按策略保留关键信息。aggressive 策略实际卸载模块释放 token，moderate 仅返回建议。
AI agents use qflow_context_compress 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 tool modifies the project context state by selectively removing or compressing information based on compression strategies (aggressive vs. moderate). While 'aggressive' strategy performs state-altering module unloading, the tool is reversible—compressed context can be reloaded or regenerated.
From the tool's definition Tool name 'qflow_context_compress' with description indicating it 'compresses context' and 'unloads modules to release tokens' under aggressive strategy.
Documented attack patterns abuse exactly the kind of access qflow_context_compress 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_compress:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_context_compress": {
"limits": [
{
"counter": "qflow_context_compress_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_context_compress 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.
压缩上下文，按策略保留关键信息。aggressive 策略实际卸载模块释放 token，moderate 仅返回建议。. 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_context_compress: 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_compress 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_context_compress 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_compress. 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_compress 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.