singularityagent__history
Recent transactions for an address on one chain, newest first. Read completeness before the entries: an empty list can mean no activity, an unconfigured indexer, or a family that cannot answer, and those are different answers. Solana, Bitcoin and Cosmos answer from their own endpoints; EVM histor...
This record as markdown: /tools/ai-rokha-rokha/singularityagent--history.md
What singularityagent__history does on Rokha
AI agents call singularityagent__history 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 |
|---|---|---|---|
chain | string | Yes | Chain id or alias. History is single-chain. |
limit | number | — | Exact entries to return. Where `budget` is also given the smaller of the two wins, so neither can talk the other into a bigger response. |
budget | string | number | — | How much of each list to return: 'small' (10 items, for a tight context), 'standard' (the default), 'full' (this source's maximum), or a number for an exact cou |
cursor | string | — | Continuation token from a previous call. Opaque — pass it back unchanged. |
address | string | Yes | Address to look up. |
Parameters from the server's own tool schema.
Why singularityagent__history is rated Low
Queries blockchain transaction history without creating, modifying, or executing operations.
From the tool's definition Recent transactions for an address, reads transaction history, no modifications.
Attacks that exploit this kind of access
The rule that runs singularityagent__history 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__history, this is the rule to start with:
singularityagent__history 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__history call is checked against it from then on.
Questions about singularityagent__history
Recent transactions for an address on one chain, newest first. Read completeness before the entries: an empty list can mean no activity, an unconfigured indexer, or a family that cannot answer, and those are different answers. Solana, Bitcoin and Cosmos answer from their own endpoints; EVM history needs SINGULARITY_ETHERSCAN_KEY and says so when it is missing rather than returning nothing. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
singularityagent__history accepts 5 parameters: chain, limit, budget, cursor, address. Required: chain, address. 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__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 Rokha. Nothing to install.
singularityagent__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 singularityagent__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 singularityagent__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.
singularityagent__history 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