Create a new journal entry on the calendar. Dates in ISO format.
AI agents use create_journal to create or update resources in CalDAV MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CalDAV MCP Server environment.
Creating a journal entry is a Write operation: it adds new data to the calendar system reversibly (entries can be edited or deleted later). It has minimal blast radius—a misbehaving agent might create unwanted journal entries, but these are easily removed. The operation is neither destructive (irreversible), executable (code/command), nor financial.
From the tool's definition Tool description states 'Create a new journal entry' — a reversible write operation that creates new data without side effects beyond the journal itself.
Attacks that exploit this kind of access
Create a new journal entry on the calendar. Dates in ISO format. It is categorised as a Write tool in the CalDAV MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CalDAV MCP Server MCP server in PolicyLayer and add a rule for create_journal: 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 CalDAV MCP Server. Nothing to install.
create_journal 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 create_journal 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 create_journal. 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.
create_journal is provided by the CalDAV MCP Server MCP server (thegreatgooo/radicale-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →