singularityagent__portfolio

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Medium RISK CLASS

Category Write

Parameters 50 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/singularityagent--portfolio.md

WHAT IT DOES

What singularityagent__portfolio does on Rokha

AI agents use singularityagent__portfolio to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.

Parameter	Type	Required	Description
`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
`chains`	array	—	Chains to query. Defaults to a spread of major chains across all four families.
`address`	string	—	One address, ENS/SNS name, or configured alias. Use `addresses` for a set.
`addresses`	array	—	Several addresses, which may span chain families. Deduplicated before querying.
`includeTokens`	boolean	—	Set false for native balances only.

Parameters from the server's own tool schema.

RISK

Why singularityagent__portfolio is rated Medium

An AI agent can call singularityagent__portfolio faster than any human can review: one bad instruction and it creates or modifies resources in Rokha by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs singularityagent__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 singularityagent__portfolio, this is the rule to start with:

singularityagent__portfolio Rate-limited

singularityagent__portfolio stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "singularityagent__portfolio": {
      "limits": [
        {
          "counter": "singularityagent__portfolio_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every singularityagent__portfolio call is checked against it from then on.

FAQ

Questions about singularityagent__portfolio

What does the singularityagent__portfolio tool do? +

Query one address, or a whole set of them, across many chains in parallel. Pass addresses when somebody holds an EVM address, a Solana pubkey and a Bitcoin address — that is one person's holdings and would otherwise be three separate questions. Each address is matched only to the chains its own format is valid on, so this is not a cross product and a Solana pubkey never produces twenty EVM errors; an address valid nowhere is reported in errors rather than failing the call. holdings is the consolidated view, by asset rather than by chain. It sums only where a sum is honest: the same token, on the same chain, across the addresses you gave. It never adds a token to itself across chains — USDC on Ethereum and USDC on Base are different contracts with different issuers of record — and never merges two contracts because they share a ticker, since only symbols this tool supplies itself are grouped by name at all. spansChains marks an asset found in more than one place. Read completeness before concluding anything is absent. Balances only: there is no fiat pricing and therefore no total value. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does singularityagent__portfolio accept? +

singularityagent__portfolio accepts 5 parameters: budget, chains, address, addresses, includeTokens. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on singularityagent__portfolio? +

Register the Rokha MCP server in PolicyLayer and add a rule for singularityagent__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.

What risk level is singularityagent__portfolio? +

singularityagent__portfolio is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit singularityagent__portfolio? +

Yes. Add a rate_limit block to the singularityagent__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.

How do I block singularityagent__portfolio completely? +

Set action: deny in the PolicyLayer policy for singularityagent__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.

What MCP server provides singularityagent__portfolio? +

singularityagent__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.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →