AI agents use move_block 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.
Moving a block changes its position or parent container within a document, altering the document's structure. This is a Write operation because the change is reversible—blocks can be moved again to restore the original state. While it modifies document content organization, it does not irreversibly delete data (which would be Destructive) nor execute arbitrary code (which would be Execute).
From the tool's definition Tool name 'move_block' and description '移动块' (move block in Chinese) indicate the tool relocates or reorders blocks within a SiYuan notebook. This is a modification operation that changes document structure reversibly.
Documented attack patterns abuse exactly the kind of access move_block 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 move_block:
{
"version": "1",
"default": "deny",
"tools": {
"move_block": {
"limits": [
{
"counter": "move_block_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_block 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 move_block: 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.
move_block 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 move_block 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 move_block. 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.
move_block 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.