New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

SERVERStellar Expert SOURCEstellar-expert-mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade A, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about get_directory_entry

What does the get_directory_entry tool do? +

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.

What parameters does get_directory_entry accept? +

get_directory_entry accepts 1 parameter: address. Required: address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_directory_entry? +

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.

What risk level is get_directory_entry? +

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

Can I rate-limit get_directory_entry? +

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.

How do I block get_directory_entry completely? +

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.

What MCP server provides get_directory_entry? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Stellar Expert's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.