set_check_item
Mark a checklist item complete or incomplete.
This record as markdown: /tools/artemnikov-trello-mcp/set-check-item.md
What set_check_item does on Trello
AI agents use set_check_item to create or update resources in Trello, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trello environment.
Why set_check_item is rated Medium
Changing a checklist item's completion status is a non-destructive write operation that modifies data but can be easily undone by toggling the status back. It affects only metadata (completion flag) on a single checklist item within Trello, with minimal blast radius if an AI agent misuses it.
From the tool's definition Tool description states 'Mark a checklist item complete or incomplete' — this modifies the state of a checklist item within a card, a reversible operation.
Attacks that exploit this kind of access
The rule that runs set_check_item safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trello, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_check_item, this is the rule to start with:
set_check_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Trello, apply this rule, and every set_check_item call is checked against it from then on.
Questions about set_check_item
Mark a checklist item complete or incomplete. It is categorised as a Write tool in the Trello MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trello MCP server in PolicyLayer and add a rule for set_check_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 Trello. Nothing to install.
set_check_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 set_check_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 set_check_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.
set_check_item is provided by the Trello MCP server (artemnikov/trello-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trello, and thousands of servers like it.
This server
Across the catalogue