Get transaction history for a linked account.
AI agents call get_transaction_history to retrieve information from Mono Banking 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 without altering, deleting, or executing external operations. It is categorized as Read. However, severity is elevated to 'high' because transaction history contains sensitive financial information that could enable fraud, money laundering detection evasion, or identity theft if accessed by a malicious agent.
From the tool's definition Tool name 'get_transaction_history' and description 'Get transaction history for a linked account' indicate data retrieval with no modification or deletion. The verb 'Get' and context of querying historical records confirm read-only semantics.
Documented attack patterns abuse exactly the kind of access get_transaction_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mono Banking MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_transaction_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_transaction_history": {}
}
}get_transaction_history 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 transaction history for a linked account. It is categorised as a Read tool in the Mono Banking MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mono Banking MCP Server MCP server in PolicyLayer and add a rule for get_transaction_history: 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 Mono Banking MCP Server. Nothing to install.
get_transaction_history 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_transaction_history 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_transaction_history. 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_transaction_history is provided by the Mono Banking MCP Server MCP server (sin4ch/mono-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Mono Banking MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 Mono Banking MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.