zest_list_assets

List all supported assets on Zest Protocol (v0-4-market). Returns the list of assets that can be supplied, borrowed, or used as collateral. Each asset includes its symbol, name, and contract ID. Supported assets: wSTX, sBTC, stSTX, USDC, USDH, stSTXbtc. Note: Zest Protocol is only available on ma...

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/zest-list-assets.md

WHAT IT DOES

What zest_list_assets does on Aibtc

AI agents call zest_list_assets 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 zest_list_assets is rated Low

This tool queries and returns static information about supported assets on the Zest Protocol. It does not create, modify, delete, or execute any operations—it merely retrieves and lists data. This is a straightforward read operation with minimal security risk.

From the tool's definition Tool name 'zest_list_assets' and description 'List all supported assets' indicate a retrieval operation with 'no side effects'. The function returns informational data about supported assets including symbol, name, and contract ID.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

zest_list_assets Allowed

zest_list_assets 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": {
    "zest_list_assets": {}
  }
}

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 zest_list_assets call is checked against it from then on.

FAQ

Questions about zest_list_assets

What does the zest_list_assets tool do? +

How do I enforce a policy on zest_list_assets? +

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

What risk level is zest_list_assets? +

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

Can I rate-limit zest_list_assets? +

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

How do I block zest_list_assets completely? +

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

What MCP server provides zest_list_assets? +

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