batch_create_tasks · Tick MCP: Risk & Policy

WHAT IT DOES

What batch_create_tasks does on Tick

AI agents use batch_create_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_create_tasks needs a policy

The tool creates new tasks in batch, which is a reversible write operation (tasks can be deleted or modified). While the description is empty, the name and context strongly indicate data creation rather than deletion or execution. The batch nature and potential to create many records simultaneously elevates severity from low to medium, but this remains Write rather than Destructive since task creation is reversible.

From the tool's definition Tool name 'batch_create_tasks' indicates creation of multiple task records. Sibling tools on the server include 'batch_delete_tasks', 'batch_update_tasks', 'complete_task', 'create_habit', 'create_project', 'create_subtask', and 'create_tag', establishing a…

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_create_tasks Rate-limited

batch_create_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_create_tasks": {
      "limits": [
        {
          "counter": "batch_create_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_create_tasks

What does the batch_create_tasks tool do? +

batch_create_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_create_tasks? +

Register the Tick MCP server in PolicyLayer and add a rule for batch_create_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_create_tasks? +

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

Can I rate-limit batch_create_tasks? +

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

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

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