AI agents call deletePackageVersion to permanently remove resources in Azure Devops — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a package version is a destructive action that cannot be undone. It permanently removes a software artifact from the package repository, which could break downstream dependencies and require recovery from backups. This is more severe than reversible write operations and meets the definition of Destructive category.
From the tool's definition Tool name is 'deletePackageVersion' with description 'Delete a version of a package'. The verb 'delete' explicitly indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access deletePackageVersion 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 deletePackageVersion:
{
"version": "1",
"default": "deny",
"hide": [
"deletePackageVersion"
]
}deletePackageVersion disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a version of a package. It is categorised as a Destructive tool in the Azure Devops MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Azure Devops MCP server in PolicyLayer and add a rule for deletePackageVersion: 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.
deletePackageVersion is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deletePackageVersion 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 deletePackageVersion. 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.
deletePackageVersion 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.
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.