Show a flat timeline of the session: nodes created + navigation events.
AI agents call session_timeline to retrieve information from MCP Roo Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and displays existing session timeline data (nodes created, navigation events). It performs no mutations, executions, or destructive operations. The verb 'Show' and the read-only nature of presenting timeline information confirm this is a Read category tool with low risk.
From the tool's definition Tool name 'session_timeline' and description 'Show a flat timeline of the session: nodes created + navigation events' indicate a retrieval/query operation that displays historical session data without modifying state.
Attacks that exploit this kind of access
Show a flat timeline of the session: nodes created + navigation events. It is categorised as a Read tool in the MCP Roo Memory MCP Server, which means it retrieves data without modifying state.
Register the MCP Roo Memory MCP server in PolicyLayer and add a rule for session_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 MCP Roo Memory. Nothing to install.
session_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 session_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 session_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.
session_timeline is provided by the MCP Roo Memory MCP server (mcasdfgf/mcp-roo-memory). 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 →