Manage note attributes with write operations (create, update, delete). Create labels (#tags), template relations (~template), update existing attributes, and organize notes with metadata. IMPORTANT: This tool only provides write access - use read_attributes to view existing attributes. Relations ...
AI agents use manage_attributes 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.
This tool creates, updates, and deletes note attributes and metadata (tags, template relations, labels). These are Write operations because they modify data reversibly—attributes can be edited or removed without permanently destroying the underlying notes. It does not execute code, delete notes themselves, or move money, placing it squarely in the Write category.
From the tool's definition Description states 'Manage note attributes with write operations (create, update, delete)' and explicitly mentions 'Create labels (#tags), template relations (~template), update existing attributes'.
Documented attack patterns abuse exactly the kind of access manage_attributes 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 manage_attributes:
{
"version": "1",
"default": "deny",
"tools": {
"manage_attributes": {
"limits": [
{
"counter": "manage_attributes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_attributes 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.
Manage note attributes with write operations (create, update, delete). Create labels (#tags), template relations (~template), update existing attributes, and organize notes with metadata. IMPORTANT: This tool only provides write access - use read_attributes to view existing attributes. Relations require values pointing to existing notes (e.g., template relations 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 manage_attributes: 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.
manage_attributes 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 manage_attributes 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 manage_attributes. 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.
manage_attributes 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.