get_ledger_device_info

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-ledger-device-info.md

WHAT IT DOES

What get_ledger_device_info does on VaultPilot MCP

AI agents call get_ledger_device_info 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.

RISK

Why get_ledger_device_info is rated Low

This tool retrieves device metadata (app name, version, connection status) with no side effects. It is purely informational and diagnostic, suitable for an agent to verify device state before performing other operations. The low severity reflects minimal blast radius—an agent cannot cause harm via this read-only query.

From the tool's definition Tool is explicitly labeled 'READ-ONLY' and 'probe the connected Ledger device' to 'report' app information. Uses a GET_APP_AND_VERSION APDU and returns device status—no data modification, deletion, execution, or financial operations occur.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_ledger_device_info Allowed

get_ledger_device_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_ledger_device_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_ledger_device_info

What does the get_ledger_device_info tool do? +

READ-ONLY — probe the connected Ledger device over USB HID and report which app is currently open (name + version), plus an actionable hint for the agent to relay. Uses the dashboard-level GET_APP_AND_VERSION APDU so it works whether the user is on the dashboard or inside a chain app — you get 'BOLOS' / 'OS' for the dashboard and e.g. 'Solana' 1.10.2 / 'Ethereum' 1.13.0 / 'Tron' 0.2.0 / 'Bitcoin' 2.3.0 when an app is open. deviceConnected: false is returned cleanly (with a hint) when no Ledger is plugged in or the udev rules are missing on Linux; the tool never throws. Call this BEFORE pair_ledger_solana / pair_ledger_tron so you can replace 'open the Solana app and enable blind-signing' with a context-aware instruction like 'I see your Bitcoin app is open — switch to Solana (device → right button → Solana → both buttons)'. One USB round-trip; no chain RPC calls. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_ledger_device_info? +

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

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

Can I rate-limit get_ledger_device_info? +

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

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

get_ledger_device_info 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 →

Across the catalogue

get_team_info on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →