signet_portfolio
Live on-chain balances: native SOL plus every non-zero SPL holding, across BOTH the Token and Token-2022 programs. With no arguments it reports every Signet session address you own. Reads only — it never signs, spends, or touches a mandate. Requires Authorization: Bearer <JWT>.
This record as markdown: /tools/ai-rokha-rokha/signet-portfolio.md
What signet_portfolio does on Rokha
AI agents call signet_portfolio 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 |
|---|---|---|---|
address | string | — | A Solana address to inspect. Omit to report your own Signet session addresses. Balances are public data. |
Parameters from the server's own tool schema.
Why signet_portfolio is rated Low
Queries blockchain data without modifying state or executing transactions.
From the tool's definition Live on-chain balances, non-zero SPL holding. Reads only — never signs, spends.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs signet_portfolio 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_portfolio, this is the rule to start with:
signet_portfolio 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_portfolio call is checked against it from then on.
Questions about signet_portfolio
Live on-chain balances: native SOL plus every non-zero SPL holding, across BOTH the Token and Token-2022 programs. With no arguments it reports every Signet session address you own. Reads only — it never signs, spends, or touches a mandate. 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_portfolio accepts 1 parameter: 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_portfolio: 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_portfolio 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_portfolio 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_portfolio. 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_portfolio 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