Taskdog

26 tools. 17 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated:

17 can modify or destroy data
9 read-only
26 tools total

Community server · catalogue entry verified 11/06/2026

How to control Taskdog ↓

What Taskdog exposes to your agents

Read (9) Write / Execute (15) Destructive / Financial (2)
Critical Risk

The most dangerous Taskdog tools

17 of Taskdog's 26 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Taskdog

PolicyLayer is an MCP gateway — it sits between your AI agents and Taskdog, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "delete_tag": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "cancel_task": {
    "limits": [
      {
        "counter": "cancel_task_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_audit_log": {
    "limits": [
      {
        "counter": "get_audit_log_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Taskdog — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON TASKDOG →

Free to start. No card required.

All 26 Taskdog tools

WRITE 15 tools
Write cancel_task Cancel a task. Changes status to CANCELED. Args: task_id: ID of the task to canc Write fix_actual_times Fix actual start/end timestamps for a task. Used to correct timestamps for historical accuracy. Past Write pause_task Pause a task (reset to PENDING). Changes status back to PENDING and clears timestamps. Args: Write remove_dependency Remove a dependency between two tasks. Args: task_id: ID of the task with the dependency Write start_task Start working on a task. Changes status from PENDING to IN_PROGRESS and records start time. Write reopen_task Reopen a completed or canceled task. Changes status back to PENDING. Args: task_ Write add_dependency Add a dependency between two tasks. The task will depend on the specified task (must be completed fir Write complete_task Mark a task as completed. Changes status to COMPLETED and records end time. Args: Write create_task Create a new task. Args: name: Task name (required) priority: Task priority ( Write decompose_task Decompose a large task into smaller subtasks. This tool helps break down complex tasks into manageabl Write optimize_schedule Auto-generate optimal task schedules. Schedules tasks with estimated_duration based on priority, dead Write restore_task Restore an archived task. Args: task_id: ID of the task to restore Returns: Write set_task_tags Set tags for a task (replaces existing tags). Args: task_id: ID of the task t Write update_task Update an existing task. Args: task_id: ID of the task to update name: New ta Write update_task_notes Update notes for a task. Args: task_id: ID of the task content: New notes con

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Taskdog

Can an AI agent delete data through the Taskdog MCP server? +

Yes. The Taskdog server exposes 2 destructive tools including delete_tag, delete_task. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Taskdog? +

The Taskdog server has 15 write tools including cancel_task, fix_actual_times, pause_task. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Taskdog.

How many tools does the Taskdog MCP server expose? +

26 tools across 4 categories: Destructive, Execute, Read, Write. 9 are read-only. 17 can modify, create, or delete data.

How do I enforce a policy on Taskdog? +

Register the Taskdog MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Taskdog tool call.

Deterministic rules across all 26 Taskdog tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

26 Taskdog tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.