Get all attributes (labels and relations) of a TriliumNext note.
AI agents call crow_trilium_get_attributes to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata (labels and relations) from a TriliumNext note without any side effects. It is a read-only query operation that does not modify, delete, or execute any actions. The blast radius is minimal since it only exposes note attributes to authorized users.
From the tool's definition Tool name contains 'get', description states 'Get all attributes' with no modification or deletion capability.
Documented attack patterns abuse exactly the kind of access crow_trilium_get_attributes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_trilium_get_attributes:
{
"version": "1",
"default": "deny",
"tools": {
"crow_trilium_get_attributes": {}
}
} crow_trilium_get_attributes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all attributes (labels and relations) of a TriliumNext note. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_trilium_get_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 Crow. Nothing to install.
crow_trilium_get_attributes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the crow_trilium_get_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 crow_trilium_get_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.
crow_trilium_get_attributes is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.