Add a new item to a checklist.
AI agents use add_checklist_item to create or update resources in Mcp Trello — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Trello environment.
This tool creates or modifies data reversibly by adding a checklist item. The action is not destructive (items can be removed), not financial, and does not execute arbitrary code or run external operations. It is a straightforward Write operation with minimal blast radius—at worst, an AI agent could spam checklist items or add unwanted items to cards, but this can be easily undone.
From the tool's definition Tool name 'add_checklist_item' and description 'Add a new item to a checklist' indicates creation of new data within an existing checklist structure.
Attacks that exploit this kind of access
Add a new item to a checklist. It is categorised as a Write tool in the Mcp Trello MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Trello 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 Mcp Trello. 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 Mcp Trello MCP server (mbeauv/mcp-trello). 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 →