list_user_tokens

List all fungible tokens owned by an address.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/list-user-tokens.md

WHAT IT DOES

What list_user_tokens does on Aibtc

AI agents call list_user_tokens to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_user_tokens is rated Low

This tool performs a read-only query to enumerate tokens at an address. It has no capability to modify, execute, or delete data. The blast radius if misused by an AI agent is minimal — it can only leak information about token holdings, not alter them or cause financial harm.

From the tool's definition Tool description states 'List all fungible tokens owned by an address' — a pure query operation that retrieves data with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_user_tokens safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_user_tokens, this is the rule to start with:

list_user_tokens Allowed

list_user_tokens is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_user_tokens": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about list_user_tokens

What does the list_user_tokens tool do? +

List all fungible tokens owned by an address. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_user_tokens? +

Register the Aibtc MCP server in PolicyLayer and add a rule for list_user_tokens: 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 Aibtc. Nothing to install.

What risk level is list_user_tokens? +

list_user_tokens is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_user_tokens? +

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

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

list_user_tokens is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →