Get recent transactions for the agent wallet.
AI agents call get_recent_transactions to retrieve information from Agent Wallet MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical transaction data from the blockchain. It performs a read-only query with no side effects, no code execution, no data modification, and no financial operations. While it's part of a wallet management system, the tool itself only accesses information. Severity is low because transaction history is typically non-sensitive metadata and reading it carries minimal risk of harm.
From the tool's definition Tool name 'get_recent_transactions' and description 'Get recent transactions for the agent wallet' indicate a retrieval operation that queries transaction history without modifying state.
Attacks that exploit this kind of access
Get recent transactions for the agent wallet. It is categorised as a Read tool in the Agent Wallet MCP MCP Server, which means it retrieves data without modifying state.
Register the Agent Wallet MCP server in PolicyLayer and add a rule for get_recent_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 Agent Wallet MCP. Nothing to install.
get_recent_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_recent_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_recent_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_recent_transactions is provided by the Agent Wallet MCP server (noah-ing/agent-wallet-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 →