get_card_history

Get the history/actions of a specific card

SERVERTrello SOURCE@delorenj/mcp-server-trello

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-delorenj-mcp-server-trello/get-card-history.md

WHAT IT DOES

What get_card_history does on Trello

AI agents call get_card_history to retrieve information from Trello without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_card_history is rated Low

This tool retrieves historical data and actions associated with a Trello card without modifying, deleting, or executing any operations. It is a pure read operation that queries existing data. Even if an AI agent misuses it by repeatedly querying card histories, the blast radius is limited to information disclosure with no destructive or financial consequences.

From the tool's definition Tool name 'get_card_history' and description 'Get the history/actions of a specific card' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_card_history Allowed

get_card_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_card_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_card_history

What does the get_card_history tool do? +

Get the history/actions of a specific card. It is categorised as a Read tool in the Trello MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_card_history? +

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

get_card_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_card_history? +

Yes. Add a rate_limit block to the get_card_history 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 get_card_history completely? +

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

get_card_history is provided by the Trello MCP server (@delorenj/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 50 Trello tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →