Bucketed message activity over time (by day or hour), in chronological order. Filterable
AI agents call timeline to retrieve information from Lore without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The timeline tool retrieves and queries historical message activity data without side effects. It is a read-only operation that aggregates and presents existing information, similar to other retrieval tools on the server (find_relevant, search_memory, get_context). The filterable aspect does not elevate it beyond Read category as it only affects which data is displayed, not the data itself.
From the tool's definition Tool provides 'Bucketed message activity over time' in 'chronological order' with filtering capability. No modification, deletion, or execution described.
Documented attack patterns abuse exactly the kind of access timeline gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lore, and nothing reaches the server without passing your rules. This is the rule we recommend for timeline:
{
"version": "1",
"default": "deny",
"tools": {
"timeline": {}
}
}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.
Bucketed message activity over time (by day or hour), in chronological order. Filterable. It is categorised as a Read tool in the Lore MCP Server, which means it retrieves data without modifying state.
Register the Lore MCP server in PolicyLayer and add a rule for 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 Lore. Nothing to install.
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 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 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.
timeline is provided by the Lore MCP server (jordanhindo/lore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lore, 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.
8 Lore tools catalogued and risk-classified — across an index of 43,000+ MCP servers.