Retrieves a list of wallets associated with the Privy application.
AI agents call get_wallets to retrieve information from Privy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only—it fetches wallet information without creating, modifying, deleting, or executing any blockchain operations. While the server context involves financial assets (wallets on blockchain), this specific tool merely lists wallets without moving funds or committing financial obligations. The blast radius of misuse is limited to information disclosure.
From the tool's definition Tool name 'get_wallets' and description 'Retrieves a list of wallets' indicate a query operation with no side effects.
Attacks that exploit this kind of access
Retrieves a list of wallets associated with the Privy application. It is categorised as a Read tool in the Privy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Privy MCP Server MCP server in PolicyLayer and add a rule for get_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 Privy MCP Server. Nothing to install.
get_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 get_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 get_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.
get_wallets is provided by the Privy MCP Server MCP server (privy-io/privy-mcp-server). 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 →