list_directory_entries
Search the StellarExpert curated Directory of well-known accounts. Filter by address list, tags (exchange, anchor, issuer, wallet, custodian, malicious, unsafe, personal, sdf, memo-required, airdrop, defi), or a search string (name/domain/address, min 5 chars). Use for reverse lookups, scam check...
This record as markdown: /tools/stellar-expert-mcp/list-directory-entries.md
What list_directory_entries does on Stellar Expert
AI agents call list_directory_entries 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 |
|---|---|---|---|
tag | array | — | Filter by Directory tags, e.g. malicious, unsafe, memo-required |
limit | integer | — | Page size (1–200). Defaults to 10 on the API. |
order | string | — | Results sort order |
cursor | string | — | paging_token from a previous page to continue |
search | string | — | Full-text search by address, name, or domain (min 5 characters) |
address | array | — | Filter by up to 50 account addresses |
Parameters from the server's own tool schema.
Why list_directory_entries is rated Low
Even though list_directory_entries 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_directory_entries 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_directory_entries, this is the rule to start with:
list_directory_entries 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_directory_entries call is checked against it from then on.
Questions about list_directory_entries
Search the StellarExpert curated Directory of well-known accounts. Filter by address list, tags (exchange, anchor, issuer, wallet, custodian, malicious, unsafe, personal, sdf, memo-required, airdrop, defi), or a search string (name/domain/address, min 5 chars). Use for reverse lookups, scam checks (tag malicious/unsafe), and labeling counterparties. It is categorised as a Read tool in the Stellar Expert MCP Server, which means it retrieves data without modifying state.
list_directory_entries accepts 6 parameters: tag, limit, order, cursor, search, address. 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_directory_entries: 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_directory_entries 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_directory_entries 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_directory_entries. 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_directory_entries 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