AI agents use rename_doc_by_id 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.
Renaming is a write operation that modifies document metadata reversibly. While not destructive (the original content is preserved and can be renamed back), it does alter the document structure. Severity is medium because renaming documents could cause workflow disruption or confusion if done incorrectly by an agent, but the operation is non-destructive and the effects are easily recoverable.
From the tool's definition Tool name 'rename_doc_by_id' and description '根据ID重命名文档' (rename document by ID) indicate modification of document metadata. This is a reversible operation that changes document names without deleting or overwriting content.
Documented attack patterns abuse exactly the kind of access rename_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 rename_doc_by_id:
{
"version": "1",
"default": "deny",
"tools": {
"rename_doc_by_id": {
"limits": [
{
"counter": "rename_doc_by_id_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_doc_by_id 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.
根据ID重命名文档. 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 rename_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.
rename_doc_by_id 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 rename_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.
Set action: deny in the PolicyLayer policy for rename_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.
rename_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.
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.