Get recent transactions for an Ethereum address
AI agents call get-transactions to retrieve information from MCP EVM Signer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads transaction history from the blockchain. It has no side effects, cannot modify data, execute code, delete records, or move funds. While the broader server manages private keys and can execute financial operations, this specific tool is a pure data retrieval function analogous to viewing account history.
From the tool's definition Tool name is 'get-transactions' and description states it 'Get recent transactions for an Ethereum address' — a query operation that retrieves historical blockchain data without modifying state or executing code.
Attacks that exploit this kind of access
Get recent transactions for an Ethereum address. It is categorised as a Read tool in the MCP EVM Signer MCP Server, which means it retrieves data without modifying state.
Register the MCP EVM Signer MCP server in PolicyLayer and add a rule for get-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 MCP EVM Signer. Nothing to install.
get-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-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-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-transactions is provided by the MCP EVM Signer MCP server (zhangzhongnan928/mcp-evm-signer). 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 →