ledger_timestamp_from_sequence
Resolve the close timestamp (UNIX + ISO date) for a given ledger sequence.
This record as markdown: /tools/stellar-expert-mcp/ledger-timestamp-from-sequence.md
What ledger_timestamp_from_sequence does on Stellar Expert
AI agents call ledger_timestamp_from_sequence 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 |
|---|---|---|---|
network | string | — | Stellar network. Defaults to STELLAR_EXPERT_NETWORK or public. |
sequence | integer | Yes | Ledger sequence number |
Parameters from the server's own tool schema.
Why ledger_timestamp_from_sequence is rated Low
Even though ledger_timestamp_from_sequence 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 ledger_timestamp_from_sequence 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 ledger_timestamp_from_sequence, this is the rule to start with:
ledger_timestamp_from_sequence 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 ledger_timestamp_from_sequence call is checked against it from then on.
Questions about ledger_timestamp_from_sequence
Resolve the close timestamp (UNIX + ISO date) for a given ledger sequence. It is categorised as a Read tool in the Stellar Expert MCP Server, which means it retrieves data without modifying state.
ledger_timestamp_from_sequence accepts 2 parameters: network, sequence. Required: sequence. 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 ledger_timestamp_from_sequence: 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.
ledger_timestamp_from_sequence 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 ledger_timestamp_from_sequence 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 ledger_timestamp_from_sequence. 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.
ledger_timestamp_from_sequence 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