list_assets
List Stellar assets with on-chain stats and StellarExpert composite rating. Search by code, issuer, home domain, or stellar.toml metadata. Sort by rating (default), created, payments, trades, trustlines, volume, or volume7d. Use to find or rank assets; rating is technical (age, activity, liquidit...
This record as markdown: /tools/stellar-expert-mcp/list-assets.md
What list_assets does on Stellar Expert
AI agents call list_assets to retrieve information from Stellar Expert 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 |
|---|---|---|---|
sort | string | — | Sort field. Defaults to rating. |
limit | integer | — | Page size (1–200). Defaults to 10 on the API. |
order | string | — | Results sort order |
cursor | integer | — | paging_token from a previous page |
search | string | — | Search by asset code, issuer, home domain, or TOML metadata |
network | string | — | Stellar network. Defaults to STELLAR_EXPERT_NETWORK or public. |
Parameters from the server's own tool schema.
Why list_assets is rated Low
Even though list_assets only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_assets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stellar Expert, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_assets, this is the rule to start with:
list_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 Stellar Expert, apply this rule, and every list_assets call is checked against it from then on.
Questions about list_assets
List Stellar assets with on-chain stats and StellarExpert composite rating. Search by code, issuer, home domain, or stellar.toml metadata. Sort by rating (default), created, payments, trades, trustlines, volume, or volume7d. Use to find or rank assets; rating is technical (age, activity, liquidity, SEP metadata), not an investment recommendation. It is categorised as a Read tool in the Stellar Expert MCP Server, which means it retrieves data without modifying state.
list_assets accepts 6 parameters: sort, limit, order, cursor, search, network. The full parameter table on this page comes from the server's own tool schema.
Register the Stellar Expert MCP server in PolicyLayer and add a rule for 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 Stellar Expert. Nothing to install.
list_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 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.
Set action: deny in the PolicyLayer policy for 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.
list_assets is provided by the Stellar Expert MCP server (stellar-expert-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stellar Expert, and thousands of servers like it.
This server
Across the catalogue