get_package_version
AI agents call get_package_version to retrieve information from Versionator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves package version and metadata information from public package registries. It performs a query operation with no side effects—it neither modifies, executes code, deletes data, nor moves money. The blast radius of misuse is minimal: an agent might query many registries rapidly (minor DoS risk) but cannot cause data loss or financial harm. Classification as Read is appropriate.
From the tool's definition Tool name is 'get_package_version'; server description states it 'queries 19 package registries (npm, PyPI, crates.io, etc.) to retrieve the latest version of packages and their metadata.' Sibling tools all follow read-only 'get_*' naming conventions…
Attacks that exploit this kind of access
get_package_version. It is categorised as a Read tool in the Versionator MCP Server, which means it retrieves data without modifying state.
Register the Versionator MCP server in PolicyLayer and add a rule for get_package_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 Versionator. Nothing to install.
get_package_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_package_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_package_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_package_version is provided by the Versionator MCP server (trianglegrrl/versionator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →