Read recent diary entries. Use to review past observations and events recorded by the agent.
AI agents call diary_read to retrieve information from ClawMem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only (reading stored diary entries). It has no capability to modify, delete, execute code, move money, or trigger external operations. The narrow scope (reading past agent observations) and local on-device nature further reduce risk. Low severity reflects minimal blast radius if an AI agent misuses it — it can only read existing context data.
From the tool's definition Tool name 'diary_read' and description explicitly states 'Read recent diary entries' with purpose to 'review past observations and events' — a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access diary_read gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ClawMem, and nothing reaches the server without passing your rules. This is the rule we recommend for diary_read:
{
"version": "1",
"default": "deny",
"tools": {
"diary_read": {}
}
}diary_read 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.
Read recent diary entries. Use to review past observations and events recorded by the agent. It is categorised as a Read tool in the ClawMem MCP Server, which means it retrieves data without modifying state.
Register the ClawMem MCP server in PolicyLayer and add a rule for diary_read: 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 ClawMem. Nothing to install.
diary_read 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 diary_read 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 diary_read. 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.
diary_read is provided by the ClawMem MCP server (yoloshii/clawmem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 ClawMem tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 ClawMem tools catalogued and risk-classified — across an index of 42,500+ MCP servers.