Medium Risk

start_task

Start working on a task. Changes status from PENDING to IN_PROGRESS and records start time. Args: task_id: ID of the task to start Returns: Updated task data with status change confirmation

How to control start_task ↓

What start_task does on Taskdog

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

Medium Risk

Why start_task needs a policy

This tool modifies task state by updating the status field and recording a timestamp. It is a reversible write operation (status can be changed back or task cancelled). No data is deleted, no code is executed, and no financial transactions occur. Blast radius is low — misuse only results in a task being incorrectly marked as in-progress.

From the tool's definition Changes status from PENDING to IN_PROGRESS and records start time

Documented attack patterns abuse exactly the kind of access start_task gives an agent:

How to control start_task

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_task": {
      "limits": [
        {
          "counter": "start_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Taskdog — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about start_task

What does the start_task tool do? +

Start working on a task. Changes status from PENDING to IN_PROGRESS and records start time. Args: task_id: ID of the task to start Returns: Updated task data with status change confirmation. It is categorised as a Write tool in the Taskdog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on start_task? +

Register the Taskdog MCP server in PolicyLayer and add a rule for start_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 Taskdog. Nothing to install.

What risk level is start_task? +

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

Can I rate-limit start_task? +

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

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

start_task is provided by the Taskdog MCP server (kohei-wada/taskdog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Taskdog tool call.

Start from Taskdog, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

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.