singularityagent__balance

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

Medium RISK CLASS

Category Write

Parameters 62 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--balance.md

WHAT IT DOES

What singularityagent__balance does on Rokha

AI agents use singularityagent__balance 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
`chain`	string	Yes	Chain id or alias, e.g. "base", "solana", "btc".
`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
`tokens`	array	—	Specific token contract addresses, mints, or denoms to check.
`address`	string	Yes	Address, ENS/SNS name, or configured alias.
`atBlock`	string \| number	—	Read state as of this block height instead of now. Supported on EVM (needs an archive endpoint) and Cosmos (needs an archive LCD). Solana and UTXO chains reject
`includeTokens`	boolean	—	Set false to fetch only the native balance (faster).

Parameters from the server's own tool schema.

RISK

Why singularityagent__balance is rated Medium

An AI agent can call singularityagent__balance 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__balance 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__balance, this is the rule to start with:

singularityagent__balance Rate-limited

singularityagent__balance 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__balance": {
      "limits": [
        {
          "counter": "singularityagent__balance_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__balance call is checked against it from then on.

FAQ

Questions about singularityagent__balance

What does the singularityagent__balance tool do? +

Native and token balances for one address on one chain. Accepts ENS/SNS names and address-book aliases. On EVM chains the token scan covers a curated set of major tokens unless you pass tokens explicitly. Pass atBlock to read a past block instead of now. 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__balance accept? +

singularityagent__balance accepts 6 parameters: chain, budget, tokens, address, atBlock, includeTokens. Required: chain, address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on singularityagent__balance? +

Register the Rokha MCP server in PolicyLayer and add a rule for singularityagent__balance: 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__balance? +

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

Can I rate-limit singularityagent__balance? +

Yes. Add a rate_limit block to the singularityagent__balance 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__balance completely? +

Set action: deny in the PolicyLayer policy for singularityagent__balance. 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__balance? +

singularityagent__balance 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 →