get_ltc_block_tip
READ-ONLY — current Litecoin mainnet chain tip. Mirror of get_btc_block_tip for Litecoin: height, 64-hex hash, timestamp, ageSeconds, optional MTP + difficulty. Backed by the configured indexer (litecoinspace.org default; LITECOIN_INDEXER_URL env var or litecoinIndexerUrl user-config override for...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-ltc-block-tip.md
What get_ltc_block_tip does on VaultPilot MCP
AI agents call get_ltc_block_tip to retrieve information from VaultPilot MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_ltc_block_tip is rated Low
This tool only retrieves blockchain state information without modification, side effects, or execution capabilities. It queries a public blockchain indexer for immutable chain tip data. The read-only designation and query-only nature (no write, execute, or financial operations) place it firmly in the Read category with low severity.
From the tool's definition Tool name includes 'get_' prefix and description explicitly states 'READ-ONLY — current Litecoin mainnet chain tip'. Returns chain metadata: height, hash, timestamp, ageSeconds, MTP, difficulty.
Attacks that exploit this kind of access
The rule that runs get_ltc_block_tip safely
PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_ltc_block_tip, this is the rule to start with:
get_ltc_block_tip 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 VaultPilot MCP, apply this rule, and every get_ltc_block_tip call is checked against it from then on.
Questions about get_ltc_block_tip
READ-ONLY — current Litecoin mainnet chain tip. Mirror of get_btc_block_tip for Litecoin: height, 64-hex hash, timestamp, ageSeconds, optional MTP + difficulty. Backed by the configured indexer (litecoinspace.org default; LITECOIN_INDEXER_URL env var or litecoinIndexerUrl user-config override for self-hosted Esplora). LTC blocks target 2.5 minutes — a 10-min gap is well within Poisson normal but worth surfacing. Issue #233 v1 (this tool was missing from the MCP surface despite the underlying indexer method existing in code). It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
Register the VaultPilot MCP server in PolicyLayer and add a rule for get_ltc_block_tip: 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 VaultPilot MCP. Nothing to install.
get_ltc_block_tip 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 get_ltc_block_tip 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 get_ltc_block_tip. 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.
get_ltc_block_tip is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on VaultPilot, and thousands of servers like it.
This server
Across the catalogue