AI agents call get_wallet 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 only retrieves and queries wallet information without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk even if misused by an AI agent, as it merely exposes existing wallet metadata.
From the tool's definition Tool description states 'Retrieve a SpherePay wallet by ID. Returns wallet details including address and network.' The verb 'Retrieve' and the read-only nature of returning wallet details with no modification capability indicate this is a data retrieval…
Attacks that exploit this kind of access
Retrieve a SpherePay wallet by ID. Returns wallet details including address and network. 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 get_wallet: 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.
get_wallet 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_wallet 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_wallet. 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_wallet 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 →