Add a checklist item (sub-task) to a task.
AI agents use add_checklist_item to create or update resources in Things Cloud MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Things Cloud MCP environment.
This tool creates a new checklist item, which is a reversible modification (can be removed). It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. While sibling tools include destructive operations (delete_task, delete_project), this specific tool is categorized as Write because it adds/creates data.
From the tool's definition Tool description states 'Add a checklist item (sub-task) to a task' — this creates new data within an existing task structure.
Attacks that exploit this kind of access
Add a checklist item (sub-task) to a task. It is categorised as a Write tool in the Things Cloud MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Things Cloud MCP server in PolicyLayer and add a rule for add_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 Things Cloud MCP. Nothing to install.
add_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 add_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 add_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.
add_checklist_item is provided by the Things Cloud MCP server (nkootstra/things). 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 →