Create a new checklist item (subtask) for a task. Checklist items help break down a task into smaller, manageable steps.
AI agents use create-checklist-item to create or update resources in My MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your My MCP environment.
This tool creates new data (checklist items) in a reversible manner. It does not execute code, delete data irreversibly, move money, or read without modification. Creation of task subtasks is a standard Write operation with minimal blast radius—worst case would be clutter from unwanted checklist items, which can be deleted via the sibling 'delete-checklist-item' tool.
From the tool's definition Tool name 'create-checklist-item' and description states 'Create a new checklist item (subtask) for a task.' The verb 'Create' and the phrase 'new checklist item' indicate data creation.
Documented attack patterns abuse exactly the kind of access create-checklist-item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and My MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create-checklist-item:
{
"version": "1",
"default": "deny",
"tools": {
"create-checklist-item": {
"limits": [
{
"counter": "create-checklist-item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-checklist-item 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.
Free to start. No card required.
Create a new checklist item (subtask) for a task. Checklist items help break down a task into smaller, manageable steps. It is categorised as a Write tool in the My MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the My MCP server in PolicyLayer and add a rule for create-checklist-item: 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 My MCP. Nothing to install.
create-checklist-item 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 create-checklist-item 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 create-checklist-item. 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.
create-checklist-item is provided by the My MCP server (jordanburke/microsoft-todo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from My MCP, 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.
16 My MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.