AI agents call memory_timeline to retrieve information from Rekal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'memory_timeline' tool most likely queries and returns historical memory or conversation timeline data without modifying the database. It appears to be a read-only introspection tool for reviewing past memories or conversations in sequence. While the empty description reduces confidence slightly, the naming and context do not suggest write, delete, or execute capabilities.
From the tool's definition Tool is named 'memory_timeline' and exists in a memory-management server alongside read operations like 'conversation_tree', 'memory_build_context', 'memory_conflicts', and 'memory_health'.
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 Rekal, 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 Rekal MCP Server, which means it retrieves data without modifying state.
Register the Rekal 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 Rekal. 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 Rekal MCP server (janbjorge/rekal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rekal, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Rekal tools catalogued and risk-classified — across an index of 43,000+ MCP servers.