AI agents call get_card_transactions to retrieve information from MBBank MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves transaction data associated with a card—a read-only operation with no side effects. However, severity is high rather than low because it exposes sensitive financial transaction history that could reveal spending patterns, merchant information, and payment details if accessed by an unauthorized AI agent or adversary.
From the tool's definition Tool name 'get_card_transactions' combined with server description stating it provides 'transaction history' and 'card details' capabilities. The 'get_' prefix and sibling tools (get_balances, get_transactions, get_cards) confirm retrieval pattern.
Documented attack patterns abuse exactly the kind of access get_card_transactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MBBank MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_card_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"get_card_transactions": {}
}
}get_card_transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_card_transactions. It is categorised as a Read tool in the MBBank MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MBBank MCP Server MCP server in PolicyLayer and add a rule for get_card_transactions: 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 MBBank MCP Server. Nothing to install.
get_card_transactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_card_transactions 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 get_card_transactions. 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.
get_card_transactions is provided by the MBBank MCP Server MCP server (thedtvn/mbbank-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MBBank MCP Server, 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.
11 MBBank MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.