migrate_workflow_states · Todos MCP: Risk & Policy

WHAT IT DOES

What migrate_workflow_states does on Todos

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

WHY IT NEEDS A POLICY

Why migrate_workflow_states needs a policy

This tool modifies workflow state metadata by synchronizing local state with canonical task statuses. While it updates data structures, the operation appears to be a data migration/synchronization task rather than destructive (no deletion indicated), financial, or code execution. The 'backfill' operation suggests it's repopulating or correcting metadata, which is a Write-class operation.

From the tool's definition The tool performs 'backfill' of workflow state metadata, which modifies existing state data. The verb 'migrate' combined with 'backfill' indicates reversible data transformation rather than deletion or code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

migrate_workflow_states Rate-limited

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

FAQ

Questions about migrate_workflow_states

What does the migrate_workflow_states tool do? +

Backfill local workflow state metadata from canonical task statuses. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on migrate_workflow_states? +

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

What risk level is migrate_workflow_states? +

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

Can I rate-limit migrate_workflow_states? +

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

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

migrate_workflow_states is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.