Check the status and details of a transaction on Rootstock blockchain using the transaction hash
AI agents call check-transaction 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.
The tool retrieves and queries transaction data from the Rootstock blockchain without creating, modifying, deleting, or executing any operations. It is a pure read operation that returns information about an existing transaction. Even in a blockchain context, transaction history queries carry minimal risk since they cannot alter state or trigger external actions.
From the tool's definition Tool name is 'check-transaction' and description states it 'Check[s] the status and details of a transaction' using only a transaction hash as input. This is a query operation with no side effects.
Attacks that exploit this kind of access
Check the status and details of a transaction on Rootstock blockchain using the transaction hash. 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: 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 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 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. 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 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 →