AI agents use flush_transaction to create or update resources in SiYuan MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SiYuan MCP Server environment.
The tool commits (writes/persists) accumulated changes to the note system. While it does not itself create, modify, or delete data directly, it finalizes Write-category operations. The transaction commit is reversible only within SiYuan's undo system, making it Write rather than Destructive.
From the tool's definition Tool name 'flush_transaction' and description '提交事务' (commit transaction) indicate finalization of pending write operations.
Documented attack patterns abuse exactly the kind of access flush_transaction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SiYuan MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for flush_transaction:
{
"version": "1",
"default": "deny",
"tools": {
"flush_transaction": {
"limits": [
{
"counter": "flush_transaction_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}flush_transaction 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 SiYuan MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SiYuan MCP Server MCP server in PolicyLayer and add a rule for flush_transaction: 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 SiYuan MCP Server. Nothing to install.
flush_transaction 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 flush_transaction 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 flush_transaction. 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.
flush_transaction is provided by the SiYuan MCP Server MCP server (xgq18237/siyuan_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 52 SiYuan MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
52 SiYuan MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.