// MCP TOOL REFERENCE

PACKAGE VERSION CHECK TOOLS

18 tools from the Package Version Check MCP Server, categorised by risk level.

// ALL 18 PACKAGE VERSION CHECK TOOLS

READ 17 tools

Read digest (optional) Package digest/hash if available. For Docker, this is the manifest digest (sha256). Read ecosystem The package ecosystem (as provided) Read error Description of the error Read inputs Action input parameters Read latest_version The latest stable version number (e.g., "1.6.5") Read lookup_errors Array of errors with: Read metadata The action.yml metadata as an object with fields: Read name The action name (as provided) Read outputs Action outputs Read package_name The package name (as provided) Read packages Array of package specifications, where each item contains: Read published_on (optional) Publication date if available (not available for Docker) Read readme (optional) The action's README content if `include_readme` was true Read result Array of successful lookups with: Read runs Execution configuration Read terraform Pin `terraform.required_version` in a file like `version.tf` or `versions.tf` Read tool_name The tool name (as provided)

EXECUTE 1 tools

Execute Example `RUN curl -LO https://dl.k8s.io/release/v1.28.0/bin/linux/amd64/kubectl`

// RUNNING THIS SERVER

The managed route: connect Package Version Check through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y package-version-check-mcp

// FAQ

How many tools does the Package Version Check MCP server have? +

The Package Version Check MCP server exposes 18 tools across 2 categories: Read, Execute.

How do I enforce policies on Package Version Check tools? +

Route the Package Version Check server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Package Version Check tools fall into? +

Package Version Check tools are categorised as Read (17), Execute (1). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.