diary_read

Read an agent

Server Exocortex shawnhack/exocortex
Category Read
Risk class Low
Parameters 00 required

What diary_read does on Exocortex

AI agents call diary_read to retrieve information from Exocortex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why diary_read needs a policy

This tool retrieves or queries data from the diary/memory system for a specific agent. It performs a read-only operation with no capability to modify, delete, or execute external actions. The minimal description and generic nature slightly lower confidence from perfect, but the 'read' semantics are clear.

From the tool's definition Tool name is 'diary_read' and description states 'Read an agent', indicating retrieval of existing data without modification or side effects.

Questions about diary_read

What does the diary_read tool do? +

Read an agent. It is categorised as a Read tool in the Exocortex MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on diary_read? +

Register the Exocortex 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 Exocortex. Nothing to install.

What risk level is diary_read? +

diary_read is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit diary_read? +

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.

How do I block diary_read completely? +

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.

What MCP server provides diary_read? +

diary_read is provided by the Exocortex MCP server (shawnhack/exocortex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.