signet_wallet_activity
A wallet's recent swaps, newest first, from Helius enhanced transactions: [{signature, time, token_in:{mint,amount}, token_out:{mint,amount}, source}]. token_in = what the wallet gave, token_out = what it got. The watch step of a copy-trade rig. Requires Authorization: Bearer <JWT>.
This record as markdown: /tools/ai-rokha-rokha/signet-wallet-activity.md
What signet_wallet_activity does on Rokha
AI agents call signet_wallet_activity 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 |
|---|---|---|---|
limit | integer | — | 1..50, default 20. |
since | integer | — | Only swaps after this unix time (seconds). |
before | string | — | Page back from this signature. |
address | string | Yes | The Solana wallet to read. |
Parameters from the server's own tool schema.
Why signet_wallet_activity is rated Low
Reads wallet transaction data without side effects, but sensitive financial information requires careful access control.
From the tool's definition wallet's recent swaps, newest first, retrieves transaction history without modification
Attacks that exploit this kind of access
The rule that runs signet_wallet_activity 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 signet_wallet_activity, this is the rule to start with:
signet_wallet_activity 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 signet_wallet_activity call is checked against it from then on.
Questions about signet_wallet_activity
A wallet's recent swaps, newest first, from Helius enhanced transactions: [{signature, time, token_in:{mint,amount}, token_out:{mint,amount}, source}]. token_in = what the wallet gave, token_out = what it got. The watch step of a copy-trade rig. Requires Authorization: Bearer <JWT>. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
signet_wallet_activity accepts 4 parameters: limit, since, before, address. Required: 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 signet_wallet_activity: 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.
signet_wallet_activity 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 signet_wallet_activity 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 signet_wallet_activity. 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.
signet_wallet_activity 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