Recent transactions for an address (~25 per call).
AI agents call get_address_transactions to retrieve information from Mcp Mempool Space 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 a public blockchain without side effects. It is informational only and does not modify state, execute code, or affect financial transactions. The data queried is already public blockchain data. Misuse by an AI agent would be benign (e.g., excessive querying, information gathering) with minimal blast radius.
From the tool's definition Tool description states 'Recent transactions for an address (~25 per call)' - this is a query/retrieval operation with no modification or execution.
Attacks that exploit this kind of access
Recent transactions for an address (~25 per call). It is categorised as a Read tool in the Mcp Mempool Space MCP Server, which means it retrieves data without modifying state.
Register the Mcp Mempool Space MCP server in PolicyLayer and add a rule for get_address_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 Mempool Space. Nothing to install.
get_address_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_address_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_address_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_address_transactions is provided by the Mcp Mempool Space MCP server (pipeworx-io/mcp-mempool-space). 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 →