put_task_checkpoint · Dag Planner MCP: Risk & Policy

WHAT IT DOES

What put_task_checkpoint does on Dag Planner

AI agents use put_task_checkpoint to create or update resources in Dag Planner — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dag Planner environment.

WHY IT NEEDS A POLICY

Why put_task_checkpoint needs a policy

This tool creates or modifies checkpoint data for a task, which is a reversible write operation (checkpoints can typically be overwritten or rolled back). It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely retrieve data (Read).

From the tool's definition Tool name 'put_task_checkpoint' and description 'Save a checkpoint for a running task' indicate modification of task state data through a write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

put_task_checkpoint Rate-limited

put_task_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "put_task_checkpoint": {
      "limits": [
        {
          "counter": "put_task_checkpoint_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dag Planner, so you can run agents against it safely.

FAQ

Questions about put_task_checkpoint

What does the put_task_checkpoint tool do? +

Save a checkpoint for a running task. It is categorised as a Write tool in the Dag Planner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on put_task_checkpoint? +

Register the Dag Planner MCP server in PolicyLayer and add a rule for put_task_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 Dag Planner. Nothing to install.

What risk level is put_task_checkpoint? +

put_task_checkpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit put_task_checkpoint? +

Yes. Add a rate_limit block to the put_task_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.

How do I block put_task_checkpoint completely? +

Set action: deny in the PolicyLayer policy for put_task_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.

What MCP server provides put_task_checkpoint? +

put_task_checkpoint is provided by the Dag Planner MCP server (shubhamnegi/dag-planner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.