task_checkpoint · AgentOS MCP: Risk & Policy

WHAT IT DOES

What task_checkpoint does on AgentOS

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

WHY IT NEEDS A POLICY

Why task_checkpoint needs a policy

This tool writes data to persistent storage (checkpoint state) without deleting or overwriting existing data irreversibly. While it modifies state, the operation is reversible—new checkpoints can overwrite old ones, and the original task continues.

From the tool's definition Tool name 'task_checkpoint' and description 'Save a checkpoint for an active task to preserve current state' indicate the tool creates or modifies state data (checkpoint records) for task resumption or recovery.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

task_checkpoint Rate-limited

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": {
    "task_checkpoint": {
      "limits": [
        {
          "counter": "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 AgentOS, so you can run agents against it safely.

FAQ

Questions about task_checkpoint

What does the task_checkpoint tool do? +

Save a checkpoint for an active task to preserve current state. It is categorised as a Write tool in the AgentOS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on task_checkpoint? +

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

What risk level is task_checkpoint? +

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

Can I rate-limit task_checkpoint? +

Yes. Add a rate_limit block to the 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 task_checkpoint completely? +

Set action: deny in the PolicyLayer policy for 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 task_checkpoint? +

task_checkpoint is provided by the AgentOS MCP server (netflypsb/agentos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.