Move a card to a different list. Use this to change a card\
AI agents use move_card to create or update resources in Trello Desktop MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trello Desktop MCP environment.
This tool modifies card data by changing its list assignment, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely retrieve data (Read).
From the tool's definition Tool name 'move_card' and description 'Move a card to a different list. Use this to change a card' indicate modification of existing card state by relocating it between lists.
Documented attack patterns abuse exactly the kind of access move_card gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trello Desktop MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for move_card:
{
"version": "1",
"default": "deny",
"tools": {
"move_card": {
"limits": [
{
"counter": "move_card_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} move_card 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.
Move a card to a different list. Use this to change a card\. It is categorised as a Write tool in the Trello Desktop MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trello Desktop MCP server in PolicyLayer and add a rule for move_card: 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 Desktop MCP. Nothing to install.
move_card 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 move_card 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 move_card. 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.
move_card is provided by the Trello Desktop MCP server (kocakli/trello-desktop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Trello Desktop 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.
19 Trello Desktop MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.