Remove tags from transaction
How to control deleteTransactionsTransactionIdRelationshipsTags ↓
AI agents call deleteTransactionsTransactionIdRelationshipsTags to permanently remove resources in Mcp Upbank — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes tags from transactions, which is a destructive operation as it irreversibly deletes tag associations. Despite the server being described as 'read-only mode', this tool clearly performs a deletion operation. The severity is medium since it only removes metadata tags rather than financial data itself, but the action cannot be undone.
From the tool's definition Tool name: 'deleteTransactionsTransactionIdRelationshipsTags', description: 'Remove tags from transaction'
Documented attack patterns abuse exactly the kind of access deleteTransactionsTransactionIdRelationshipsTags gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Upbank, and nothing reaches the server without passing your rules. This is the rule we recommend for deleteTransactionsTransactionIdRelationshipsTags:
{
"version": "1",
"default": "deny",
"hide": [
"deleteTransactionsTransactionIdRelationshipsTags"
]
} deleteTransactionsTransactionIdRelationshipsTags disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove tags from transaction. It is categorised as a Destructive tool in the Mcp Upbank MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Upbank MCP server in PolicyLayer and add a rule for deleteTransactionsTransactionIdRelationshipsTags: 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 Mcp Upbank. Nothing to install.
deleteTransactionsTransactionIdRelationshipsTags 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 deleteTransactionsTransactionIdRelationshipsTags 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 deleteTransactionsTransactionIdRelationshipsTags. 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.
deleteTransactionsTransactionIdRelationshipsTags is provided by the Mcp Upbank MCP server (sirmews/mcp-upbank). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Upbank, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Mcp Upbank tools catalogued and risk-classified — across an index of 43,000+ MCP servers.