TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT

Permanently removes a specified attachment from a Trello card; this action is irreversible and requires that both the card and the attachment exist.

SERVERTrello SOURCEmcp-server-trello

Critical RISK CLASS

Category Destructive

Parameters 20 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trello/trello-delete-cards-attachments-by-id-card-by-id-attachment.md

WHAT IT DOES

What TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT does on Trello

AI agents call TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT to permanently remove resources in Trello, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`idCard`	string	—	The ID or short link of the card from which the attachment will be deleted. Card IDs can be short (e.g., 'FY2OWrnc') or long (e.g., '571d07b591c8b68aeb4f6acc').
`idAttachment`	string	—	The ID of the attachment to be deleted from the card. This is a unique identifier for the attachment.

Parameters from the server's own tool schema.

RISK

Why TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT is rated Critical

The tool description explicitly states it 'permanently removes' an attachment and is 'irreversible', which matches the Destructive category definition of actions that cannot be undone. While the blast radius is somewhat contained (only one attachment per invocation), the permanent nature of deletion and inability to recover the data without external backups justifies 'high' severity.

From the tool's definition Permanently removes a specified attachment from a Trello card; this action is irreversible

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT 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_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT, this is the rule to start with:

TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT Hidden

TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Trello, apply this rule, and every TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT call is checked against it from then on.

FAQ

Questions about TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT

What does the TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT tool do? +

Permanently removes a specified attachment from a Trello card; this action is irreversible and requires that both the card and the attachment exist. It is categorised as a Destructive tool in the Trello MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT accept? +

TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT accepts 2 parameters: idCard, idAttachment. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT? +

Register the Trello MCP server in PolicyLayer and add a rule for TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT: 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.

What risk level is TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT? +

TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT? +

Yes. Add a rate_limit block to the TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT 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.

How do I block TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT completely? +

Set action: deny in the PolicyLayer policy for TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT. 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.

What MCP server provides TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT? +

TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT 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.

KEEP EXPLORING

More on Trello, and thousands of servers like it.

This server

All 200 Trello tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →