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

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.

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

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.

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

Questions about ledger_sequence_from_timestamp

What does the ledger_sequence_from_timestamp tool do? +

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.

What parameters does ledger_sequence_from_timestamp accept? +

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.

How do I enforce a policy on ledger_sequence_from_timestamp? +

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.

What risk level is ledger_sequence_from_timestamp? +

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

Can I rate-limit ledger_sequence_from_timestamp? +

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.

How do I block ledger_sequence_from_timestamp completely? +

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.

What MCP server provides ledger_sequence_from_timestamp? +

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.

Across the catalogue

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