auto_assign_task · Todos MCP: Risk & Policy

WHAT IT DOES

What auto_assign_task does on Todos

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

The tool modifies task state by assigning ownership to an agent. While reversible (tasks can be reassigned), it is a state-changing write operation rather than a read. Severity is medium because incorrect auto-assignment could misdirect work or create workflow inefficiencies, but it lacks the irreversibility of destructive operations or the external execution risk of Execute category tools.

From the tool's definition Tool description states it will 'assign a task', which modifies task ownership/state. This is a write operation that creates or modifies task metadata (the assigned agent), similar to other Write operations like 'add_task_dependency' and 'add_comment' on this…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auto_assign_task Rate-limited

auto_assign_task 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": {
    "auto_assign_task": {
      "limits": [
        {
          "counter": "auto_assign_task_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 auto_assign_task

What does the auto_assign_task tool do? +

Automatically assign a task to the best-fit agent based on capabilities, current load, and focus mode. 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 auto_assign_task? +

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

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

Can I rate-limit auto_assign_task? +

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

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

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