Categorize transaction
How to control patchTransactionsTransactionIdRelationshipsCategory ↓
AI agents use patchTransactionsTransactionIdRelationshipsCategory to create or update resources in Mcp Upbank — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Upbank environment.
This tool creates or modifies transaction category relationships, which is reversible data modification. Although the server claims read-only operation, this PATCH endpoint allows changing how transactions are categorized. The severity is medium because miscategorization affects financial organization and reporting but does not delete data or move funds.
From the tool's definition Tool name contains 'patch' (HTTP PATCH method for updates) and 'Relationships'; description states 'Categorize transaction' which modifies transaction metadata.
Documented attack patterns abuse exactly the kind of access patchTransactionsTransactionIdRelationshipsCategory 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 patchTransactionsTransactionIdRelationshipsCategory:
{
"version": "1",
"default": "deny",
"tools": {
"patchTransactionsTransactionIdRelationshipsCategory": {
"limits": [
{
"counter": "patchtransactionstransactionidrelationshipscategory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}patchTransactionsTransactionIdRelationshipsCategory stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Categorize transaction. It is categorised as a Write tool in the Mcp Upbank MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Upbank MCP server in PolicyLayer and add a rule for patchTransactionsTransactionIdRelationshipsCategory: 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.
patchTransactionsTransactionIdRelationshipsCategory 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 patchTransactionsTransactionIdRelationshipsCategory 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 patchTransactionsTransactionIdRelationshipsCategory. 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.
patchTransactionsTransactionIdRelationshipsCategory 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.