get_update_command

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-update-command.md

WHAT IT DOES

What get_update_command does on VaultPilot MCP

AI agents call get_update_command 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_update_command is rated Low

This tool only retrieves and compares version information from process metadata and cached npm registry data. It provides informational output about available updates but does not execute any installation, modification, or command—it merely recommends an upgrade flow. The explicit 'READ-ONLY' designation confirms it performs no state changes or external operations.

From the tool's definition Tool description explicitly states 'READ-ONLY' and describes it as returning recommended upgrade information by examining process arguments and comparing cached version data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_update_command Allowed

get_update_command 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_update_command": {}
  }
}

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_update_command call is checked against it from then on.

FAQ

Questions about get_update_command

What does the get_update_command tool do? +

READ-ONLY — return the recommended upgrade flow for the running install path. Combines (1) process.argv/process.execPath heuristics that classify the install as one of npm-global / npx / bundled-binary / from-source / unknown with (2) cached state from the once-per-session npm-registry version check the server already runs lazily on first tool call. Returns: current (server version), latest (most recent npm registry response, or null if the lazy check hasn't resolved yet), updateAvailable (strict-newer comparator), installPath (detected kind), command (the one-liner to run), restartHint (post-upgrade restart note), and an optional note field that flags caveats (unknown install path → defer to INSTALL.md; unresolved version check → can re-run). AGENT BEHAVIOR: call this when the user asks to upgrade, when the VAULTPILOT NOTICE — Update available block appears and the user wants to act on it, or when the user asks 'how do I update vaultpilot-mcp'. Surface command to the user verbatim — do not execute it autonomously. The detection is a heuristic; if installPath is unknown, ask the user which install path they used. Pure local introspection + cache read; no RPC, no fresh network call (the kickoff already did that). Never throws. 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_update_command? +

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

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

Can I rate-limit get_update_command? +

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

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

get_update_command 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_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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