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

Agent View of the PolicyLayer registry record for `get_directory_entry`. HTML page: https://policylayer.com/tools/stellar-expert-mcp/get-directory-entry

## Facts

- Tool: `get_directory_entry`
- Server: Stellar Expert (`stellar-expert-mcp`) — https://policylayer.com/tools/stellar-expert-mcp.md
- Install: `npx -y stellar-expert-mcp`
- Homepage: https://www.npmjs.com/package/stellar-expert-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `address` | string | yes | Stellar account address (G followed by 55 base32 characters) |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_directory_entry",
    "arguments": {
      "address": "<address>"
    }
  }
}
```

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

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Stellar Expert:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_directory_entry": {}
  }
}
```

## Other tools on Stellar Expert (11)

- `check_blocked_domain` — Read — https://policylayer.com/tools/stellar-expert-mcp/check-blocked-domain.md
- `get_asset_holder_rank` — Read — https://policylayer.com/tools/stellar-expert-mcp/get-asset-holder-rank.md
- `get_asset_rating` — Read — https://policylayer.com/tools/stellar-expert-mcp/get-asset-rating.md
- `get_asset_supply` — Read — https://policylayer.com/tools/stellar-expert-mcp/get-asset-supply.md
- `ledger_sequence_from_timestamp` — Read — https://policylayer.com/tools/stellar-expert-mcp/ledger-sequence-from-timestamp.md
- `ledger_timestamp_from_sequence` — Read — https://policylayer.com/tools/stellar-expert-mcp/ledger-timestamp-from-sequence.md
- `list_asset_holders` — Read — https://policylayer.com/tools/stellar-expert-mcp/list-asset-holders.md
- `list_assets` — Read — https://policylayer.com/tools/stellar-expert-mcp/list-assets.md
- `list_blocked_domains` — Read — https://policylayer.com/tools/stellar-expert-mcp/list-blocked-domains.md
- `list_directory_entries` — Read — https://policylayer.com/tools/stellar-expert-mcp/list-directory-entries.md
- `list_directory_tags` — Read — https://policylayer.com/tools/stellar-expert-mcp/list-directory-tags.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=stellar-expert-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/stellar-expert-mcp
