AI agents call list_bank_accounts to retrieve information from Smokeball without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves bank account information for the firm without creating, modifying, deleting, or executing any operations. While bank account information is sensitive, the read-only nature and lack of action capability (no transfers, payments, or modifications) places it in the Read category with low severity, as an AI agent misusing this would only be able to view account data, not perform financial transactions.
From the tool's definition Tool name and description indicate 'List bank accounts' which is a retrieval operation with no side effects. The verb 'list' and the action of querying existing bank account data confirms read-only behavior.
Attacks that exploit this kind of access
List bank accounts (trust, operating) for this firm. It is categorised as a Read tool in the Smokeball MCP Server, which means it retrieves data without modifying state.
Register the Smokeball MCP server in PolicyLayer and add a rule for list_bank_accounts: 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 Smokeball. Nothing to install.
list_bank_accounts 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 list_bank_accounts 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 list_bank_accounts. 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.
list_bank_accounts is provided by the Smokeball MCP server (rosenadvertising/smokeball-mcp). 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 →