Delete a wiki
AI agents call delete_wiki to permanently remove resources in Azure DevOps MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a wiki, which is an irreversible action that destroys data and cannot be undone. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' Severity is high because deletion of an entire wiki affects all its content and collaborative information, but the blast radius depends on the…
From the tool's definition Tool name is 'delete_wiki' with description 'Delete a wiki'. The verb 'delete' is explicit and irreversible.
Attacks that exploit this kind of access
Delete a wiki. It is categorised as a Destructive tool in the Azure DevOps MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for delete_wiki: 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 MCP Server. Nothing to install.
delete_wiki 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 delete_wiki 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 delete_wiki. 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.
delete_wiki is provided by the Azure DevOps MCP Server MCP server (jaybird-us/azure-devops-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 →