Check the transaction history of a wallet on Rootstock blockchain using Alchemy API
AI agents call check-transaction-history to retrieve information from RSK MCP Server - Rootstock Blockchain Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and queries transaction data—a core Read operation. It has no capability to transfer funds, deploy contracts, modify state, or execute code. The blast radius of misuse is minimal (information disclosure limited to historical transactions accessible to the target wallet). Low severity is appropriate for a data retrieval operation with no side effects.
From the tool's definition Tool name 'check-transaction-history' and description 'Check the transaction history of a wallet' indicate a query operation that retrieves historical data from the Rootstock blockchain via Alchemy API with no state modifications.
Attacks that exploit this kind of access
Check the transaction history of a wallet on Rootstock blockchain using Alchemy API. It is categorised as a Read tool in the RSK MCP Server - Rootstock Blockchain Tools MCP Server, which means it retrieves data without modifying state.
Register the RSK MCP Server - Rootstock Blockchain Tools MCP server in PolicyLayer and add a rule for check-transaction-history: 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 RSK MCP Server - Rootstock Blockchain Tools. Nothing to install.
check-transaction-history 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 check-transaction-history 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 check-transaction-history. 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.
check-transaction-history is provided by the RSK MCP Server - Rootstock Blockchain Tools MCP server (rsksmart/rsk-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 →