AI agents call get_transactions to retrieve information from Tiller Money MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although this is a read-only operation (low capability risk), it accesses sensitive financial transaction data which could expose personal banking information, account balances, spending patterns, and other confidential financial details if an AI agent misuses the access. The high severity reflects the sensitivity of the data exposed, not the nature of the operation itself.
From the tool's definition Server description states 'Provides read-only access to Tiller Money financial data' and tool is sibling to get_accounts, get_categories, get_transaction_details which are all read operations.
Documented attack patterns abuse exactly the kind of access get_transactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tiller Money MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"get_transactions": {}
}
}get_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_transactions. It is categorised as a Read tool in the Tiller Money MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tiller Money MCP Server MCP server in PolicyLayer and add a rule for get_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 Tiller Money MCP Server. Nothing to install.
get_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_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_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_transactions is provided by the Tiller Money MCP Server MCP server (jackstein21/tiller-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tiller Money 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.
4 Tiller Money MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.