list_checkpoints
List installed checkpoint models visible to ComfyUI and the fast SDXL runner.
This record as markdown: /tools/mcp-control-plane/list-checkpoints.md
What list_checkpoints does on Mcp Control Plane
AI agents call list_checkpoints to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_checkpoints is rated Low
This tool retrieves and enumerates checkpoint models available to ComfyUI and SDXL runners. It performs data discovery without modifying, executing, or deleting any resources. The information returned may help an agent understand available ML models, but misuse carries minimal risk—the worst outcome is wasted context or incorrect model selection, not data loss or code execution.
From the tool's definition Tool name 'list_checkpoints' and description 'List installed checkpoint models' indicate a query/retrieval operation with no side effects. The verb 'list' is a canonical Read operation.
Attacks that exploit this kind of access
The rule that runs list_checkpoints safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_checkpoints, this is the rule to start with:
list_checkpoints is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every list_checkpoints call is checked against it from then on.
Questions about list_checkpoints
List installed checkpoint models visible to ComfyUI and the fast SDXL runner. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.
Register the Mcp Control Plane 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 Mcp Control Plane. 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 Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
This server
Across the catalogue