Delete a wiki page
AI agents call delete_wiki_page 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.
Deleting a wiki page is an irreversible operation that permanently removes documentation content. This cannot be undone by normal means and represents data loss. While the blast radius is scoped to a single wiki page (not system-wide), the destructive nature of the operation and potential impact on team documentation warrants a 'high' severity classification.
From the tool's definition Tool name is 'delete_wiki_page' with description 'Delete a wiki page'. The verb 'delete' directly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a wiki page. 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_page: 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_page 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_page 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_page. 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_page 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 →