AI agents call memory_timeline to retrieve information from Cortex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the naming convention and the function of sibling tools in the Cortex memory system, 'memory_timeline' most likely retrieves temporal or historical memory records. There is no evidence of modification, deletion, or execution of external operations.
From the tool's definition Tool name 'memory_timeline' combined with sibling tools like 'memory_get', 'memory_list', 'memory_recall', and 'memory_remind' strongly suggests this retrieves or queries memory data.
Documented attack patterns abuse exactly the kind of access memory_timeline gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cortex, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_timeline:
{
"version": "1",
"default": "deny",
"tools": {
"memory_timeline": {}
}
}memory_timeline 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.
memory_timeline. It is categorised as a Read tool in the Cortex MCP Server, which means it retrieves data without modifying state.
Register the Cortex 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 Cortex. 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 Cortex MCP server (tt-wang/memem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Cortex tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Cortex tools catalogued and risk-classified — across an index of 42,500+ MCP servers.