batch_update_tasks · Tick MCP: Risk & Policy

WHAT IT DOES

What batch_update_tasks does on Tick

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

WHY IT NEEDS A POLICY

Why batch_update_tasks needs a policy

The tool creates or modifies task data reversibly—a Write category action. Severity is medium because batch operations on tasks could disrupt user workflows if misused, but updates are not irreversible like deletions. Confidence is lowered to 0.75 due to lack of explicit description; inferred from naming and sibling context.

From the tool's definition Tool name 'batch_update_tasks' indicates modification of multiple task records. No description provided, but context from sibling tools (batch_create_tasks, batch_delete_tasks, complete_task, create_task, create_subtask) confirms this server manages TickTick…

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_update_tasks Rate-limited

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

FAQ

Questions about batch_update_tasks

What does the batch_update_tasks tool do? +

batch_update_tasks. It is categorised as a Write tool in the Tick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on batch_update_tasks? +

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

What risk level is batch_update_tasks? +

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

Can I rate-limit batch_update_tasks? +

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

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

batch_update_tasks is provided by the Tick MCP server (kpihx/tick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.