Get the full historical timeline of a memory, including all its versions and updates.
AI agents call get_timeline to retrieve information from memro MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only operations on historical memory data. It queries and returns version history without creating, modifying, deleting, or executing anything. The action is non-destructive and has no side effects beyond information retrieval. Severity is low because misuse would only expose historical information without enabling harmful actions.
From the tool's definition Tool name is 'get_timeline' and description states it retrieves 'the full historical timeline of a memory, including all its versions and updates.' The verbs 'get' and 'retrieve' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get the full historical timeline of a memory, including all its versions and updates. It is categorised as a Read tool in the memro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the memro MCP Server MCP server in PolicyLayer and add a rule for get_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 memro MCP Server. Nothing to install.
get_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 get_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 get_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.
get_timeline is provided by the memro MCP Server MCP server (memrohq/memro-mcp). 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 →