add_task_run_event · Todos MCP: Risk & Policy

WHAT IT DOES

What add_task_run_event does on Todos

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

This tool creates or modifies task run event records. While it records various event types (progress, comments, status changes), these are reversible operations - events can typically be edited, superseded, or their state reverted in a task management system. It does not irreversibly delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).

From the tool's definition Tool description states it can 'Record a local run event' with multiple types including 'progress, comment, claim, command, file, artifact, completed, failed, or cancelled' - these are reversible modifications to task run state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_task_run_event Rate-limited

add_task_run_event 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": {
    "add_task_run_event": {
      "limits": [
        {
          "counter": "add_task_run_event_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 add_task_run_event

What does the add_task_run_event tool do? +

Record a local run event such as progress, comment, claim, command, file, artifact, completed, failed, or cancelled. 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 add_task_run_event? +

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

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

Can I rate-limit add_task_run_event? +

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

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

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