Create a journal entry with file attachments (photos, videos, audio, PDFs)
AI agents use create_entry_with_attachments to create or update resources in MCP-DayOne — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-DayOne environment.
This tool creates new journal entries with attachments, which is a reversible write operation. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), involves no financial transactions (ruling out Financial), and retrieves no data (ruling out Read).
From the tool's definition Tool name contains 'create' and description states 'Create a journal entry with file attachments', indicating creation of new data records in the Day One journal system.
Documented attack patterns abuse exactly the kind of access create_entry_with_attachments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-DayOne, and nothing reaches the server without passing your rules. This is the rule we recommend for create_entry_with_attachments:
{
"version": "1",
"default": "deny",
"tools": {
"create_entry_with_attachments": {
"limits": [
{
"counter": "create_entry_with_attachments_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_entry_with_attachments 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.
Create a journal entry with file attachments (photos, videos, audio, PDFs). It is categorised as a Write tool in the MCP-DayOne MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-DayOne MCP server in PolicyLayer and add a rule for create_entry_with_attachments: 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 MCP-DayOne. Nothing to install.
create_entry_with_attachments 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_entry_with_attachments 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_entry_with_attachments. 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_entry_with_attachments is provided by the MCP-DayOne MCP server (quevin/mcp-dayone). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-DayOne, 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.
10 MCP-DayOne tools catalogued and risk-classified — across an index of 43,000+ MCP servers.