update_my_progress · Dag Planner MCP: Risk & Policy

WHAT IT DOES

What update_my_progress does on Dag Planner

AI agents use update_my_progress 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 update_my_progress needs a policy

This tool creates or modifies data (progress state, working output, checkpoints) in a reversible manner. It does not execute external operations, delete data, or move money. The severity is medium rather than low because incorrect updates to task progress in a dependency graph could cause downstream tasks to proceed with wrong assumptions, potentially leading to wasted computation or incorrect results.

From the tool's definition Tool description states 'Update working output and optionally checkpoint progress' - the verb 'update' indicates modification of existing data. The context of a DAG task planner suggests this modifies task state, progress tracking, or intermediate outputs.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_my_progress Rate-limited

update_my_progress 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": {
    "update_my_progress": {
      "limits": [
        {
          "counter": "update_my_progress_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 update_my_progress

What does the update_my_progress tool do? +

Update working output and optionally checkpoint progress. 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 update_my_progress? +

Register the Dag Planner MCP server in PolicyLayer and add a rule for update_my_progress: 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 update_my_progress? +

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

Can I rate-limit update_my_progress? +

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

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

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