Return the on-chain balance for one Litecoin mainnet address via the Esplora indexer (litecoinspace.org by default; override via LITECOIN_INDEXER_URL env var or userConfig.litecoinIndexerUrl). Returns confirmed + mempool litoshis and an LTC-decimal projection. Accepts L/M/3/ltc1q/ltc1p — the read...
AI agents call get_ltc_balance to retrieve information from VaultPilot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | Yes | Litecoin mainnet address. Accepts legacy (L...), P2SH (M...), legacy P2SH (3...), native segwit (ltc1q...), or taproot (ltc1p...). Note that Litecoin Core has n |
Parameters from the server's own tool schema.
Even though get_ltc_balance 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
Return the on-chain balance for one Litecoin mainnet address via the Esplora indexer (litecoinspace.org by default; override via LITECOIN_INDEXER_URL env var or userConfig.litecoinIndexerUrl). Returns confirmed + mempool litoshis and an LTC-decimal projection. Accepts L/M/3/ltc1q/ltc1p — the read path validates format only. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_ltc_balance accepts 1 parameter: address. Required: address. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for get_ltc_balance: 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_balance 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_balance 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_balance. 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_balance 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.