three_balance
Return the $THREE and SOL balance for a Solana pubkey. If no pubkey is given, uses the configured signer (SOLANA_SECRET_KEY). Read-only — no payment.
This record as markdown: /tools/io-github-nirholas-three-token-mcp/three-balance.md
What three_balance does on $THREE Token
AI agents call three_balance to retrieve information from $THREE Token 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 |
|---|---|---|---|
pubkey | string | — | Base58 pubkey to read. Defaults to the configured signer's address. |
Parameters from the server's own tool schema.
Why three_balance is rated Low
This tool queries blockchain state to retrieve token and SOL balances for a given Solana public key. It performs no writes, executions, deletions, or financial transactions. The explicit 'Read-only' designation and absence of payment mechanisms confirm this is a data retrieval operation with no side effects.
From the tool's definition Tool description explicitly states 'Return the $THREE and SOL balance' and 'Read-only — no payment.' The tool retrieves balance data without modifying state or executing side effects.
Attacks that exploit this kind of access
The rule that runs three_balance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and $THREE Token, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For three_balance, this is the rule to start with:
three_balance 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 $THREE Token, apply this rule, and every three_balance call is checked against it from then on.
Questions about three_balance
Return the $THREE and SOL balance for a Solana pubkey. If no pubkey is given, uses the configured signer (SOLANA_SECRET_KEY). Read-only — no payment. It is categorised as a Read tool in the $THREE Token MCP Server, which means it retrieves data without modifying state.
three_balance accepts 1 parameter: pubkey. The full parameter table on this page comes from the server's own tool schema.
Register the $THREE Token MCP server in PolicyLayer and add a rule for three_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 $THREE Token. Nothing to install.
three_balance 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 three_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.
Set action: deny in the PolicyLayer policy for three_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.
three_balance is provided by the $THREE Token MCP server (@three-ws/three-token-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on $THREE Token, and thousands of servers like it.
This server
Across the catalogue