AI agents call get_saving_details 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.
The naming pattern 'get_*' combined with the server's stated purpose of providing 'monitoring and analytics capabilities' and the absence of destructive keywords (delete, modify, transfer) indicates this tool retrieves savings information without side effects. Confidence is slightly reduced due to empty description, but sibling tool patterns strongly support Read classification.
From the tool's definition Tool name 'get_saving_details' indicates a retrieval operation. Context shows sibling tools (get_balances, get_transactions, get_cards, get_savings) that are clearly read operations. Description is empty, limiting direct evidence.
Documented attack patterns abuse exactly the kind of access get_saving_details 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_saving_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_saving_details": {}
}
}get_saving_details 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_saving_details. 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_saving_details: 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_saving_details 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_saving_details 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_saving_details. 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_saving_details 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.