singularityagent__transaction
Fetch and normalize a transaction, with EVM calldata decoded where the selector is recognized. If no chain is given, searches the chains the hash format allows and reports every chain it was found on. Read finality alongside status, because they answer different questions: status says the chain e...
This record as markdown: /tools/ai-rokha-rokha/singularityagent--transaction.md
What singularityagent__transaction does on Rokha
AI agents call singularityagent__transaction to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
hash | string | Yes | Transaction hash, txid, or Solana signature. |
chain | string | — | Chain id, to skip the cross-chain search. |
Parameters from the server's own tool schema.
Why singularityagent__transaction is rated Low
Tool only retrieves and normalizes blockchain transaction data with no side effects.
From the tool's definition Fetch and normalize a transaction...decoded where the selector is recognized
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs singularityagent__transaction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For singularityagent__transaction, this is the rule to start with:
singularityagent__transaction is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every singularityagent__transaction call is checked against it from then on.
Questions about singularityagent__transaction
Fetch and normalize a transaction, with EVM calldata decoded where the selector is recognized. If no chain is given, searches the chains the hash format allows and reports every chain it was found on. Read finality alongside status, because they answer different questions: status says the chain executed the transaction and it did not revert, while finality says whether the block holding it can still be discarded. final is the only kind that licenses an irreversible decision. reversible means it sits at or near the head and a reorganization would erase it. probabilistic is proof-of-work settlement — it carries a confirmation count and never becomes final at any depth, because the chain offers no point past which reversal is disallowed, only one past which it is expensive; how many confirmations are enough is the caller’s decision. unknown means the endpoint would not say, which is not evidence that it is settled. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
singularityagent__transaction accepts 2 parameters: hash, chain. Required: hash. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for singularityagent__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 Rokha. Nothing to install.
singularityagent__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 singularityagent__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 singularityagent__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.
singularityagent__transaction is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue