add-comments
AI agents use add-comments 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.
Adding comments creates new data within Trello cards (reversible action). While the tool description is empty, the name combined with the server's documented capability to support 'adding comments' clearly indicates a Write operation. Severity is medium because comment spam or malicious comments could degrade card usability, but comments are easily deleted and don't cause irreversible data loss or financial impact.
From the tool's definition Tool name 'add-comments' and server description stating 'adding comments' indicates creation of new comment data on Trello cards. Description field is empty, lowering confidence slightly.
Attacks that exploit this kind of access
add-comments. 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 add-comments: 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.
add-comments 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 add-comments 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 add-comments. 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.
add-comments 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 →