AI agents use trello_action to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
due | string | — | Due date as ISO 8601 string. |
pos | string | — | Card position: top, bottom, or a positive float. |
desc | string | — | Card description. |
name | string | — | Card name (for create_card and update_card). |
limit | number | — | Max results for search_cards. |
query | string | — | Search query (for search_cards). |
token | string | Yes | Trello user token. |
action | string | Yes | Action: get_boards, get_lists, get_cards, create_card, update_card, search_cards. |
closed | boolean | — | Archive or unarchive the card. |
filter | string | — | Filter for boards or lists: open, closed, all. |
api_key | string | Yes | Trello API key. |
card_id | string | — | Card ID (for update_card). |
Parameters from the server's own tool schema.
The tool performs reversible data modifications (creating and updating Trello cards), fitting the Write category. While it includes read operations, the creation and modification of cards represent the primary risk—a compromised agent could spam, manipulate, or corrupt project management data.
From the tool's definition Tool description explicitly states it can "create cards, and update card properties" on Trello, which are write operations.
Risk signalsAccepts freeform code/query input (query) · Handles credentials or secrets (api_key) · High parameter count (17 properties)
Attacks that exploit this kind of access
Interact with the Trello REST API: list boards and lists, get and search cards, create cards, and update card properties. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
trello_action accepts 12 parameters: due, pos, desc, name, limit, query, token, action, closed, filter, api_key, card_id. Required: token, action, api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for trello_action: 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 UnClick. Nothing to install.
trello_action 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 trello_action 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 trello_action. 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.
trello_action is provided by the UnClick MCP server (@unclick/mcp-server). 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 →