Add or remove a tag from a card.
AI agents call tag_card to permanently remove resources in Favro MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call tag_card doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Favro MCP is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Add or remove a tag from a card. It is categorised as a Destructive tool in the Favro MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Favro MCP server in PolicyLayer and add a rule for tag_card: 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 Favro MCP. Nothing to install.
tag_card is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the tag_card 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 tag_card. 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.
tag_card is provided by the Favro MCP server (truls27a/favro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.