add_todo · Decision Tree MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_todo does on Decision Tree MCP Server

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

WHY IT NEEDS A POLICY

Why add_todo needs a policy

This tool creates or modifies data (a new to-do item) in a reversible manner. It does not execute code, delete data, move money, or trigger external operations. It fits the Write category. Severity is low because: (1) the blast radius is limited to to-do list entries, (2) the data is non-critical and reversible (can be deleted), and (3) misuse poses minimal risk to system integrity or user safety.

From the tool's definition Tool name 'add_todo' and description 'Add task to to-do list' indicate creation of new task data stored in Redis. The action creates reversible data without side effects beyond the to-do list itself.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_todo Rate-limited

add_todo 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_todo": {
      "limits": [
        {
          "counter": "add_todo_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 Decision Tree MCP Server, so you can run agents against it safely.

FAQ

Questions about add_todo

What does the add_todo tool do? +

Add task to to-do list. It is categorised as a Write tool in the Decision Tree MCP Server 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_todo? +

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

What risk level is add_todo? +

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

Can I rate-limit add_todo? +

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

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

add_todo is provided by the Decision Tree MCP Server MCP server (psikosen/dt_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.