Create a new real checkpoint of RiderProjects directory
AI agents use create_checkpoint to create or update resources in MCP Conductor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Conductor environment.
This tool creates a checkpoint (a snapshot or backup state) of the RiderProjects directory. While it modifies system state by adding new checkpoint data, the operation is reversible (checkpoints can be deleted or replaced), and there is no irreversible data destruction. It does not execute arbitrary commands, move financial resources, or require destructive permissions.
From the tool's definition Tool is named 'create_checkpoint' and described as 'Create a new real checkpoint of RiderProjects directory'. The verb 'Create' indicates a write operation that generates a new checkpoint snapshot.
Documented attack patterns abuse exactly the kind of access create_checkpoint gives an agent:
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 create_checkpoint:
{
"version": "1",
"default": "deny",
"tools": {
"create_checkpoint": {
"limits": [
{
"counter": "create_checkpoint_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_checkpoint stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new real checkpoint of RiderProjects directory. It is categorised as a Write tool in the MCP Conductor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Conductor MCP server in PolicyLayer and add a rule for create_checkpoint: 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.
create_checkpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_checkpoint 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 create_checkpoint. 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.
create_checkpoint 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.
Start from MCP Conductor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 MCP Conductor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.