binance_us_cust_supported_assets
Get list of assets supported for custodial solution transfers and settlements. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Response includes: - transferEligible: Assets that can be transferred - settlementEligible: Assets that can be settled Each asset entry contains: - asset: Asset symbol - precision...
This record as markdown: /tools/nirholas-binance-mcp/binance-us-cust-supported-assets.md
What binance_us_cust_supported_assets does on Binance MCP Server
AI agents call binance_us_cust_supported_assets to retrieve information from Binance MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why binance_us_cust_supported_assets is rated Low
This is a read-only information retrieval tool. However, severity is elevated to 'medium' rather than 'low' because: (1) it requires custodial API key access, indicating privileged account context; (2) the information returned (asset eligibility, network support, precision details) could be used to inform financial decisions or identify transfer capabilities for subsequent financial operations; (3) while this tool…
From the tool's definition Tool retrieves a list of supported assets for custodial transfers and settlements. Description states 'Get list of assets' which is a pure query operation with no side effects. Returns asset metadata (symbol, precision, network) without modifying data.
Attacks that exploit this kind of access
The rule that runs binance_us_cust_supported_assets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Binance MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For binance_us_cust_supported_assets, this is the rule to start with:
binance_us_cust_supported_assets 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 Binance MCP Server, apply this rule, and every binance_us_cust_supported_assets call is checked against it from then on.
Questions about binance_us_cust_supported_assets
Get list of assets supported for custodial solution transfers and settlements. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Response includes: - transferEligible: Assets that can be transferred - settlementEligible: Assets that can be settled Each asset entry contains: - asset: Asset symbol - precision: Decimal precision - network: Supported blockchain networks. It is categorised as a Read tool in the Binance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance MCP Server MCP server in PolicyLayer and add a rule for binance_us_cust_supported_assets: 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 Binance MCP Server. Nothing to install.
binance_us_cust_supported_assets 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 binance_us_cust_supported_assets 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 binance_us_cust_supported_assets. 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.
binance_us_cust_supported_assets is provided by the Binance MCP Server MCP server (nirholas/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Binance MCP Server, and thousands of servers like it.
This server
Across the catalogue