生成会话交接摘要（包含当前进度、待办事项、关键决策）
AI agents use qflow_session_handoff 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 creates new structured data artifacts (session handoff summaries) that capture project state information. While the handoff summary itself is not destructive and doesn't involve financial operations, it represents a Write operation that creates or modifies documentation/records.
From the tool's definition Tool generates and creates session handoff summaries containing current progress, pending items, and key decisions. The verb 'generates' and the nature of creating summary artifacts indicates data creation/modification rather than simple retrieval.
Documented attack patterns abuse exactly the kind of access qflow_session_handoff 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_session_handoff:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_session_handoff": {
"limits": [
{
"counter": "qflow_session_handoff_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_session_handoff 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.
生成会话交接摘要（包含当前进度、待办事项、关键决策）. 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_session_handoff: 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_session_handoff 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_session_handoff 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_session_handoff. 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_session_handoff 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.