get_latest_version
Latest published version + deprecation flag — the cheapest call. USE WHEN: only a version string matters (pinning a dep, answering 'what version of X'). If you also need health/vulns use check_package. RETURNS: {latest, deprecated, published_at}.
This record as markdown: /tools/dev-depscope-mcp/get-latest-version.md
What get_latest_version does on Depscope
AI agents call get_latest_version to retrieve information from Depscope without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
package | string | Yes | |
ecosystem | string | Yes |
Parameters from the server's own tool schema.
Why get_latest_version is rated Low
This tool retrieves and queries package version metadata without side effects. It reads publicly available information about the latest version of a package and whether it is deprecated. No data is created, modified, deleted, or executed. The worst-case misuse would be retrieving version information repeatedly, which poses minimal risk. Classified as Read with low severity.
From the tool's definition The tool returns 'Latest published version + deprecation flag' and explicitly states it is 'the cheapest call' used 'WHEN: only a version string matters'.
Attacks that exploit this kind of access
The rule that runs get_latest_version safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Depscope, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_latest_version, this is the rule to start with:
get_latest_version is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Depscope, apply this rule, and every get_latest_version call is checked against it from then on.
Questions about get_latest_version
Latest published version + deprecation flag — the cheapest call. USE WHEN: only a version string matters (pinning a dep, answering 'what version of X'). If you also need health/vulns use check_package. RETURNS: {latest, deprecated, published_at}. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
get_latest_version accepts 2 parameters: package, ecosystem. Required: package, ecosystem. The full parameter table on this page comes from the server's own tool schema.
Register the Depscope MCP server in PolicyLayer and add a rule for get_latest_version: 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 Depscope. Nothing to install.
get_latest_version 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_latest_version 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_latest_version. 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_latest_version is provided by the Depscope MCP server (cuttalo/depscope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Depscope, and thousands of servers like it.
This server
Across the catalogue