TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD
Generates a new calendar key for the Trello board specified by idBoard, invalidating any previous key for that board.
This record as markdown: /tools/trello/trello-add-boards-calendar-key-generate-by-id-board.md
What TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD does on Trello
AI agents use TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
idBoard | string | — | The unique identifier of the Trello board for which to generate a calendar key. |
Parameters from the server's own tool schema.
Why TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD is rated Medium
This tool creates a new credential (calendar key) and overwrites/invalidates the previous one. While it modifies access credentials rather than board data directly, it is reversible and represents a state change in the Trello board's configuration. This fits the Write category (creates/modifies data reversibly).
From the tool's definition Generates a new calendar key for the Trello board...invalidating any previous key
Attacks that exploit this kind of access
The rule that runs TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD 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 TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD, this is the rule to start with:
TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD 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 TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD call is checked against it from then on.
Questions about TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD
Generates a new calendar key for the Trello board specified by idBoard, invalidating any previous key for that board. 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.
TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD accepts 1 parameter: idBoard. The full parameter table on this page comes from the server's own tool schema.
Register the Trello MCP server in PolicyLayer and add a rule for TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD: 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.
TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD 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_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD 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_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD. 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_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD is provided by the Trello MCP server (mcp-server-trello). 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