AI agents call memory_timeline 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.
The tool's core function is to query and retrieve temporal/historical metadata about memories and decisions. The verbs used ('Query', 'decision history', 'evolution') all indicate data retrieval with no side effects. No creation, modification, deletion, or execution of external operations is described. This fits squarely into the Read category as a lookup/search operation on existing memory data.
From the tool's definition Tool name and description indicate querying/retrieval functions: 'Query decision history, memory lineage, topic evolution, or temporal hierarchy' — all read-only operations that retrieve historical information without modifying data.
Attacks that exploit this kind of access
Query decision history, memory lineage, topic evolution, or temporal hierarchy. It is categorised as a Read tool in the Exocortex MCP Server, which means it retrieves data without modifying state.
Register the Exocortex MCP server in PolicyLayer and add a rule for memory_timeline: 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.
memory_timeline 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 memory_timeline 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 memory_timeline. 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.
memory_timeline 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.
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 →