AI agents call list_virtual_account_transfers to retrieve information from SpherePay without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays transfer records for a virtual account. It has no side effects, does not execute operations, does not modify data, and does not move money. While the broader SpherePay service involves financial operations, this specific tool is a read-only query that merely surfaces existing transaction history.
From the tool's definition Tool name contains 'list' and description states 'List transfers... Shows deposit activity and conversion history' — these are read-only query operations that retrieve historical data without modification.
Attacks that exploit this kind of access
List transfers for a specific virtual account. Shows deposit activity and conversion history. It is categorised as a Read tool in the SpherePay MCP Server, which means it retrieves data without modifying state.
Register the SpherePay MCP server in PolicyLayer and add a rule for list_virtual_account_transfers: 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 SpherePay. Nothing to install.
list_virtual_account_transfers 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_virtual_account_transfers 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_virtual_account_transfers. 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_virtual_account_transfers is provided by the SpherePay MCP server (danchev/spherepay-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 →