move-cards
AI agents use move-cards to create or update resources in Trello MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trello MCP Server environment.
Move-cards modifies card state (position/list assignment) but does not delete data or execute arbitrary code. It is reversible and represents a Write operation. Severity is medium because bulk operations ('move-cards' implies multiple) across a workspace could disrupt team workflows if misapplied, but the action is not destructive or financial.
From the tool's definition Tool name 'move-cards' and sibling tools include 'create-card', 'archive-card', 'add-comment', 'add-label'—all Write operations. Moving cards modifies their list/position state reversibly within Trello boards.
Attacks that exploit this kind of access
move-cards. It is categorised as a Write tool in the Trello MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trello MCP Server MCP server in PolicyLayer and add a rule for move-cards: 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 MCP Server. Nothing to install.
move-cards 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-cards 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-cards. 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-cards is provided by the Trello MCP Server MCP server (praveencs87/trello-mcp). 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 →