update_subtask · TaskMateAI MCP: Risk & Policy

WHAT IT DOES

What update_subtask does on TaskMateAI

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

WHY IT NEEDS A POLICY

Why update_subtask needs a policy

The tool modifies subtask records by updating their status field. This is a reversible write operation — the status can be changed again if needed. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). Given the task management context and sibling tools like complete_task and update_progress, this clearly performs data modification.

From the tool's definition Tool name 'update_subtask' combined with description stating it updates subtask status ('サブタスクのステータスを更新します' = 'Updates the status of subtasks'). This is a modification operation that changes existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_subtask Rate-limited

update_subtask 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": {
    "update_subtask": {
      "limits": [
        {
          "counter": "update_subtask_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 TaskMateAI, so you can run agents against it safely.

FAQ

Questions about update_subtask

What does the update_subtask tool do? +

サブタスクのステータスを更新します。. It is categorised as a Write tool in the TaskMateAI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_subtask? +

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

What risk level is update_subtask? +

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

Can I rate-limit update_subtask? +

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

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

update_subtask is provided by the TaskMateAI MCP server (newaitees/taskmateai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.