Update note with support for title-only updates, content overwrite, content append, or file replacement. ⚠️ REQUIRED: ALWAYS call get_note first to obtain current hash. ⚠️ SIMPLER RULES: Note type and MIME type are IMMUTABLE - cannot be changed after creation. MODE SELECTION: Use
AI agents use update_note to create or update resources in TriliumNext Notes' MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TriliumNext Notes' MCP Server environment.
The update_note tool creates or modifies data in a reversible manner (update operations can be undone by applying a new update). While it does warn about obtaining the current hash and notes immutable properties, the core function is to modify note content, titles, and files—classic Write category behavior.
From the tool's definition Tool description states 'Update note' with capabilities including 'title-only updates, content overwrite, content append, or file replacement'. These are all reversible modifications to existing data.
Documented attack patterns abuse exactly the kind of access update_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TriliumNext Notes' MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_note:
{
"version": "1",
"default": "deny",
"tools": {
"update_note": {
"limits": [
{
"counter": "update_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_note 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.
Update note with support for title-only updates, content overwrite, content append, or file replacement. ⚠️ REQUIRED: ALWAYS call get_note first to obtain current hash. ⚠️ SIMPLER RULES: Note type and MIME type are IMMUTABLE - cannot be changed after creation. MODE SELECTION: Use. It is categorised as a Write tool in the TriliumNext Notes' MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TriliumNext Notes' MCP Server MCP server in PolicyLayer and add a rule for update_note: 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 TriliumNext Notes' MCP Server. Nothing to install.
update_note 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 update_note 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 update_note. 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.
update_note is provided by the TriliumNext Notes' MCP Server MCP server (tan-yong-sheng/triliumnext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 TriliumNext Notes' MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 TriliumNext Notes' MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.