merge_tasks · Todos MCP: Risk & Policy

WHAT IT DOES

What merge_tasks does on Todos

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

The merge operation modifies existing data structures (combining tasks, updating relationships, preserving history) but does not permanently delete the original tasks or prevent undo. It is a consolidation/modification action rather than deletion (Destructive) or code execution (Execute).

From the tool's definition Tool description states it 'Merge[s] duplicate tasks into a primary record, preserving comments/commits/files and audit history' — this modifies task records by consolidating them and updating data associations, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_tasks Rate-limited

merge_tasks 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": {
    "merge_tasks": {
      "limits": [
        {
          "counter": "merge_tasks_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 merge_tasks

What does the merge_tasks tool do? +

Merge duplicate tasks into a primary record, preserving comments/commits/files and audit history. 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 merge_tasks? +

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

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

Can I rate-limit merge_tasks? +

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

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

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