AI agents use bulk_create_tasks to create or update resources in Todos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.
This tool creates new task records in bulk, which is a reversible write operation. While it could potentially flood the system with many tasks if misused by an agent, the effects are not destructive (tasks can be deleted) and not financial. The blast radius is moderate—an agent could create excessive tasks causing noise/confusion—justifying medium severity.
From the tool's definition Tool name 'bulk_create_tasks' and description 'Create multiple tasks at once from an array of task objects' indicate data creation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Create multiple tasks at once from an array of task objects. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todos MCP server in PolicyLayer and add a rule for bulk_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 Todos. Nothing to install.
bulk_create_tasks is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bulk_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.
Set action: deny in the PolicyLayer policy for bulk_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.
bulk_create_tasks is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →