Low Risk

getPackageVersions

Get versions of a package in a feed

How to control getPackageVersions ↓

AI agents call getPackageVersions to retrieve information from Azure Devops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves metadata about package versions from an Azure DevOps feed. It performs a read-only operation that queries existing data without side effects, creating, modifying, executing code, or deleting anything. The blast radius of misuse is minimal — an agent could only retrieve information already present in the feed.

From the tool's definition Tool name is 'getPackageVersions' and description states 'Get versions of a package in a feed' — both indicate a query/retrieval operation with no modification or execution of code.

Documented attack patterns abuse exactly the kind of access getPackageVersions gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Azure Devops, and nothing reaches the server without passing your rules. This is the rule we recommend for getPackageVersions:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getPackageVersions": {}
  }
}

getPackageVersions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Azure Devops — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the getPackageVersions tool do? +

Get versions of a package in a feed. It is categorised as a Read tool in the Azure Devops MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getPackageVersions? +

Register the Azure Devops MCP server in PolicyLayer and add a rule for getPackageVersions: 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 Azure Devops. Nothing to install.

What risk level is getPackageVersions? +

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

Can I rate-limit getPackageVersions? +

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

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

getPackageVersions is provided by the Azure Devops MCP server (ryancardin15/azuredevops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Azure Devops tool call.

Deterministic rules across all 97 Azure Devops tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

97 Azure Devops tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.