AI agents use set_due_complete 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.
The tool modifies card state (setting completion status) but does not create/delete data irreversibly or trigger external operations. It is a metadata update similar to other Write-category tools on this Trello server. Severity is low because changing completion status on a task management card is a low-risk operation with no blast radius to system integrity or data permanence.
From the tool's definition Tool is named 'set_due_complete' and marks a card as complete. This is a reversible state change operation on card metadata (marking completion status), consistent with Write operations like 'add_comment' and 'add_label' on the same server.
Documented attack patterns abuse exactly the kind of access set_due_complete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trello, and nothing reaches the server without passing your rules. This is the rule we recommend for set_due_complete:
{
"version": "1",
"default": "deny",
"tools": {
"set_due_complete": {
"limits": [
{
"counter": "set_due_complete_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_due_complete 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.
Mark a card. 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_due_complete: 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_due_complete 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_due_complete 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_due_complete. 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_due_complete is provided by the Trello MCP server (v4lheru/trello-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Trello, 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.
76 Trello tools catalogued and risk-classified — across an index of 43,000+ MCP servers.