list_checkpoints

THE RISK

Low Risk

Why list_checkpoints needs a policy

The tool retrieves and enumerates checkpoint data without creating, modifying, deleting, or executing operations. It is a simple read operation that queries the state of the orchestration system's checkpoint storage. The blast radius of misuse is minimal - an agent could only gain visibility into existing checkpoints, not manipulate them.

From the tool's definition Tool name is 'list_checkpoints' and description states 'List all available real checkpoints' - this is a query/listing operation with no modification or execution of side effects.

Documented attack patterns abuse exactly the kind of access list_checkpoints gives an agent:

POLICY

How to control list_checkpoints

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Conductor, and nothing reaches the server without passing your rules. This is the rule we recommend for list_checkpoints:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_checkpoints": {}
  }
}

list_checkpoints is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MCP Conductor — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Conductor tools

Write initialize_luther_rules Initialize Luther\ Write compress_context Compress conversation context using intelligent algorithms Write coordinate_checkpoint Create a coordinated checkpoint across multiple MCPs Write create_checkpoint Create a new real checkpoint of RiderProjects directory Write create_project_intelligence_cache Create comprehensive project intelligence cache to eliminate session startup overhead Write create_session_rule Create a new persistent session rule (stored in Memory MCP) Write create_unified_handoff Create a coordinated handoff package using all 5 MCPs Write invalidate_project_cache Invalidate project intelligence cache when major changes occur

All 25 MCP Conductor tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_checkpoints

What does the list_checkpoints tool do? +

List all available real checkpoints. It is categorised as a Read tool in the MCP Conductor MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_checkpoints? +

Register the MCP Conductor 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 Conductor. Nothing to install.

What risk level is list_checkpoints? +

list_checkpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_checkpoints? +

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.

How do I block list_checkpoints completely? +

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.

What MCP server provides list_checkpoints? +

list_checkpoints is provided by the MCP Conductor MCP server (lutherscottgarcia/mcp-conductor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Conductor tool call.

Start from MCP Conductor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →