Medium Risk

transfer_block_ref

转移块引用

How to control transfer_block_ref ↓

AI agents use transfer_block_ref 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.

Medium Risk

Transferring a block reference means updating/modifying existing references from one block to another. This is a reversible write operation that modifies data (block references) within SiYuan Note. The description is minimal but the operation implies updating references rather than deleting or executing code. Confidence is moderate due to limited description detail.

From the tool's definition Tool name 'transfer_block_ref' and description '转移块引用' (transfer block reference)

Documented attack patterns abuse exactly the kind of access transfer_block_ref 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 transfer_block_ref:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_block_ref": {
      "limits": [
        {
          "counter": "transfer_block_ref_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

transfer_block_ref 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.

  1. Create a free account and register SiYuan MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the transfer_block_ref tool do? +

转移块引用. 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.

How do I enforce a policy on transfer_block_ref? +

Register the SiYuan MCP Server MCP server in PolicyLayer and add a rule for transfer_block_ref: 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.

What risk level is transfer_block_ref? +

transfer_block_ref is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit transfer_block_ref? +

Yes. Add a rate_limit block to the transfer_block_ref 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.

How do I block transfer_block_ref completely? +

Set action: deny in the PolicyLayer policy for transfer_block_ref. 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.

What MCP server provides transfer_block_ref? +

transfer_block_ref 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.

Enforce policy on every SiYuan MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.