AI agents call get_cards 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 card information from a bank account without creating, modifying, deleting, or executing any operations. It is purely informational/read access. The medium severity reflects that card details are sensitive financial information that could be used to facilitate fraud if combined with other capabilities (e.g., start_transfer), but the tool itself performs no destructive, financial, or executable…
From the tool's definition Tool name 'get_cards' and description 'Get the cards associated with the MB Bank account' indicate a retrieval operation with no modification or execution. The verb 'Get' and the passive structure confirm a read-only action.
Documented attack patterns abuse exactly the kind of access get_cards 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_cards:
{
"version": "1",
"default": "deny",
"tools": {
"get_cards": {}
}
}get_cards 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 the cards associated with the MB Bank account. 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_cards: 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_cards 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_cards 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_cards. 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_cards 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.