AI agents call list_offloader_wallets 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 wallet information with pagination support. It is purely a read operation that queries existing data without creating, modifying, deleting, or executing any actions. The low severity reflects that unauthorized access would expose wallet data but carries minimal blast radius compared to tools like execute_transfer (which moves money) or execute_script (which runs code).
From the tool's definition Tool name contains 'list' and description states 'List SpherePay offloader wallets with pagination' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List SpherePay offloader wallets with pagination. 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_offloader_wallets: 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_offloader_wallets 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_offloader_wallets 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_offloader_wallets. 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_offloader_wallets 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 →