Critical Risk →

remove_doc_by_id

根据ID删除文档

How to control remove_doc_by_id ↓

AI agents call remove_doc_by_id to permanently remove resources in SiYuan MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool permanently deletes documents by their ID without reversibility. Document deletion cannot be undone and represents permanent data loss. This is classified as Destructive rather than Write because the operation is irreversible. Severity is high because bulk or mistaken deletions could result in significant data loss, though the blast radius depends on document scope and permissions.

From the tool's definition Tool name 'remove_doc_by_id' and description '根据ID删除文档' (delete document by ID) indicate irreversible deletion of documents.

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_doc_by_id"
  ]
}

remove_doc_by_id disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  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.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the remove_doc_by_id tool do? +

根据ID删除文档. It is categorised as a Destructive tool in the SiYuan MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_doc_by_id? +

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

remove_doc_by_id is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_doc_by_id? +

Yes. Add a rate_limit block to the remove_doc_by_id 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 remove_doc_by_id completely? +

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

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