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

ledger_timestamp_from_sequence

Resolve the close timestamp (UNIX + ISO date) for a given ledger sequence.

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

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

Questions about ledger_timestamp_from_sequence

What does the ledger_timestamp_from_sequence tool do? +

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.

What parameters does ledger_timestamp_from_sequence accept? +

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.

How do I enforce a policy on ledger_timestamp_from_sequence? +

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.

What risk level is ledger_timestamp_from_sequence? +

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

Can I rate-limit ledger_timestamp_from_sequence? +

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.

How do I block ledger_timestamp_from_sequence completely? +

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.

What MCP server provides ledger_timestamp_from_sequence? +

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.

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.