List all available checkpoints for the current session. Shows when each was created and any notes attached.
AI agents call list_checkpoints to retrieve information from Context Travel MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays metadata about existing checkpoints without altering, deleting, or executing any operations. It is a straightforward read-only query operation that has no blast radius if misused by an AI agent.
From the tool's definition Tool name is 'list_checkpoints' and description states it 'List all available checkpoints' and 'Shows when each was created and any notes attached' — purely a retrieval/query operation with no modification or side effects.
Attacks that exploit this kind of access
List all available checkpoints for the current session. Shows when each was created and any notes attached. It is categorised as a Read tool in the Context Travel MCP MCP Server, which means it retrieves data without modifying state.
Register the Context Travel MCP server in PolicyLayer and add a rule for list_checkpoints: 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 Context Travel MCP. Nothing to install.
list_checkpoints 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 list_checkpoints 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 list_checkpoints. 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.
list_checkpoints is provided by the Context Travel MCP server (simen/mcp-memento). 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 →