Retrieves transaction history for a specific wallet.
AI agents call get_wallet_transactions 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 fetch historical transaction data. It has no side effects, does not modify blockchain state, does not execute arbitrary code, and does not involve financial movements. While the server context involves blockchain and financial assets, this specific tool only retrieves information.
From the tool's definition Tool name 'get_wallet_transactions' and description 'Retrieves transaction history' indicate a query operation that reads blockchain data without modifying state.
Attacks that exploit this kind of access
Retrieves transaction history for a specific wallet. 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_transactions: 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_transactions 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_transactions 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_transactions. 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_transactions 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 →