sign_message_ltc

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

High RISK CLASS

Category Execute

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/sign-message-ltc.md

WHAT IT DOES

What sign_message_ltc does on VaultPilot MCP

AI agents invoke sign_message_ltc to trigger actions in VaultPilot MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`wallet`	string	Yes	Paired Litecoin source address. Must already be in `pairings.litecoin`. Taproot (`ltc1p...`) is refused — BIP-322 is not yet exposed by the Ledger Litecoin app.
`message`	string	Yes	UTF-8 message to sign.

Parameters from the server's own tool schema.

RISK

Why sign_message_ltc is rated High

This tool triggers a cryptographic signing operation on a hardware device (Ledger). It does not directly transfer funds or modify on-chain state, but it executes an external operation (device interaction, producing a cryptographic signature) whose effects depend on the message content.

From the tool's definition Sign a UTF-8 message with a paired Litecoin address using the BIP-137 compact-signature scheme... Returns the signature plus messageSha256... Same on-device clear-sign UX as sign_message_btc

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sign_message_ltc 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 sign_message_ltc, this is the rule to start with:

sign_message_ltc Rate-limited

sign_message_ltc stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sign_message_ltc": {
      "limits": [
        {
          "counter": "sign_message_ltc_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every sign_message_ltc call is checked against it from then on.

FAQ

Questions about sign_message_ltc

What does the sign_message_ltc tool do? +

Sign a UTF-8 message with a paired Litecoin address using the BIP-137 compact-signature scheme (with Litecoin's \x19Litecoin Signed Message:\n prefix). Returns the signature plus messageSha256 — lowercase hex SHA-256 of the exact UTF-8 bytes submitted to the device (Inv #8 byte-fingerprint, issue #454); surface in the verbatim block so the user can recompute on a separate device. Same on-device clear-sign UX as sign_message_btc. DRAINER-STRING REFUSAL (issue #454): refuses messages containing value-transfer / authorization markers or explicit drainer templates BEFORE any device interaction — same allowlist as sign_message_btc. Taproot (ltc1p…) is refused — BIP-322 isn't exposed by the Ledger Litecoin app. It is categorised as a Execute tool in the VaultPilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does sign_message_ltc accept? +

sign_message_ltc accepts 2 parameters: wallet, message. Required: wallet, message. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sign_message_ltc? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for sign_message_ltc: 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.

What risk level is sign_message_ltc? +

sign_message_ltc is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sign_message_ltc? +

Yes. Add a rate_limit block to the sign_message_ltc 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 sign_message_ltc completely? +

Set action: deny in the PolicyLayer policy for sign_message_ltc. 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 sign_message_ltc? +

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

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →