memory_auto

All-in-one memory tool. Understands natural language:

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

What memory_auto does on Exocortex

AI agents call memory_auto 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 memory_auto needs a policy

Despite the vague description 'Understands natural language', the tool's role in a hybrid RAG retrieval system and positioning alongside specialized read tools indicates it primarily retrieves or queries stored memories. The lack of any language suggesting write, execute, delete, or financial capabilities places it in the Read category.

From the tool's definition Tool description states it 'Understands natural language' and is part of a memory system with sibling tools like 'diary_read', 'memory_browse', and 'memory_clip'.

Questions about memory_auto

What does the memory_auto tool do? +

All-in-one memory tool. Understands natural language:. 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 memory_auto? +

Register the Exocortex MCP server in PolicyLayer and add a rule for memory_auto: 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 memory_auto? +

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

Can I rate-limit memory_auto? +

Yes. Add a rate_limit block to the memory_auto 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 memory_auto completely? +

Set action: deny in the PolicyLayer policy for memory_auto. 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 memory_auto? +

memory_auto 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.