get_directory_entry
Look up one Stellar account in the Directory. Returns name, domain, and tags when listed. An empty object (or 404) means the account is not in the Directory — it may still exist on-chain.
This record as markdown: /tools/stellar-expert-mcp/get-directory-entry.md
What get_directory_entry does on Stellar Expert
AI agents call get_directory_entry 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 |
|---|---|---|---|
address | string | Yes | Stellar account address (G followed by 55 base32 characters) |
Parameters from the server's own tool schema.
Why get_directory_entry is rated Low
Even though get_directory_entry 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 get_directory_entry 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 get_directory_entry, this is the rule to start with:
get_directory_entry 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 get_directory_entry call is checked against it from then on.
Questions about get_directory_entry
Look up one Stellar account in the Directory. Returns name, domain, and tags when listed. An empty object (or 404) means the account is not in the Directory — it may still exist on-chain. It is categorised as a Read tool in the Stellar Expert MCP Server, which means it retrieves data without modifying state.
get_directory_entry accepts 1 parameter: address. Required: 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 get_directory_entry: 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.
get_directory_entry 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 get_directory_entry 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 get_directory_entry. 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.
get_directory_entry 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