Retrieves details for a specific wallet by its ID.
AI agents call get_wallet_details 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 a read-only operation to retrieve wallet information. While it operates in a financial context (blockchain wallets), it does not move money, execute transactions, modify data, or perform any destructive actions. It simply queries and returns existing wallet details, making it a Read category tool with low severity.
From the tool's definition Tool name 'get_wallet_details' and description 'Retrieves details for a specific wallet by its ID' indicate a query operation that fetches data without modification or side effects.
Attacks that exploit this kind of access
Retrieves details for a specific wallet by its ID. 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_wallet_details: 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_wallet_details 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_details 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_details. 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_details 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 →