List all checkpoints in the document history
AI agents call list_checkpoints to retrieve information from AI-Canvas MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about existing checkpoints. It has no side effects, does not modify data, does not delete anything, and does not trigger external operations. It is purely informational, falling squarely into the Read category with low severity since the blast radius of misuse is confined to information disclosure about design document history.
From the tool's definition The tool name is 'list_checkpoints' and the description states it 'List all checkpoints in the document history' — this is a query/retrieval operation that retrieves checkpoint metadata without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
List all checkpoints in the document history. It is categorised as a Read tool in the AI-Canvas MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AI-Canvas MCP Server 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 AI-Canvas MCP Server. 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 AI-Canvas MCP Server MCP server (laoluojuhai/ai-canvas). 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 →