Get a specific bank account transaction by ID.
AI agents call get_bank_account_transaction to retrieve information from Buildium 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 an existing bank account transaction without modifying, deleting, or executing any operations. It has no side effects and poses minimal risk—at most an information disclosure concern if sensitive financial data is exposed, but the retrieval itself is a read-only operation. No financial transactions are initiated or modified.
From the tool's definition Tool name is 'get_bank_account_transaction' and description states 'Get a specific bank account transaction by ID.' The verb 'Get' and the word 'by ID' indicate a query/retrieval operation.
Attacks that exploit this kind of access
Get a specific bank account transaction by ID. It is categorised as a Read tool in the Buildium MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Buildium MCP Server MCP server in PolicyLayer and add a rule for get_bank_account_transaction: 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 Buildium MCP Server. Nothing to install.
get_bank_account_transaction 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_bank_account_transaction 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_bank_account_transaction. 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_bank_account_transaction is provided by the Buildium MCP Server MCP server (luthersystems/mcp-server-buildium). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →