Get or create today
AI agents use crow_trilium_day_note to create or update resources in Crow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
The tool performs a reversible write operation (creating or retrieving a daily note). It does not execute arbitrary code, delete data irreversibly, or handle financial operations. The scope is limited to managing a single day's note in a project management system. Severity is low because the operation is confined to note management with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name indicates 'day_note' creation capability. Description states 'Get or create today' which explicitly includes a create operation.
Documented attack patterns abuse exactly the kind of access crow_trilium_day_note 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_day_note:
{
"version": "1",
"default": "deny",
"tools": {
"crow_trilium_day_note": {
"limits": [
{
"counter": "crow_trilium_day_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} crow_trilium_day_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.
Get or create today. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for crow_trilium_day_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 Crow. Nothing to install.
crow_trilium_day_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 crow_trilium_day_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 crow_trilium_day_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.
crow_trilium_day_note 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.