ledger_sequence_from_timestamp
Resolve the ledger sequence whose close time is equal to or before the given timestamp (UNIX seconds or RFC 3339). Returns 404 if the time is before the first ledger or in the future.
This record as markdown: /tools/stellar-expert-mcp/ledger-sequence-from-timestamp.md
What ledger_sequence_from_timestamp does on Stellar Expert
AI agents call ledger_sequence_from_timestamp 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. |
timestamp | string | number | Yes | UNIX time (seconds) or RFC 3339 timestamp, e.g. 1642597270 or 2022-08-29T13:51:18Z |
Parameters from the server's own tool schema.
Why ledger_sequence_from_timestamp is rated Low
Even though ledger_sequence_from_timestamp 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_sequence_from_timestamp 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_sequence_from_timestamp, this is the rule to start with:
ledger_sequence_from_timestamp 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_sequence_from_timestamp call is checked against it from then on.
Questions about ledger_sequence_from_timestamp
Resolve the ledger sequence whose close time is equal to or before the given timestamp (UNIX seconds or RFC 3339). Returns 404 if the time is before the first ledger or in the future. It is categorised as a Read tool in the Stellar Expert MCP Server, which means it retrieves data without modifying state.
ledger_sequence_from_timestamp accepts 2 parameters: network, timestamp. Required: timestamp. 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_sequence_from_timestamp: 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_sequence_from_timestamp 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_sequence_from_timestamp 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_sequence_from_timestamp. 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_sequence_from_timestamp 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