Update content of an existing wiki page or create a new page if it does not exist
AI agents use wiki_update_page to create or update resources in Azure DevOps Wiki MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure DevOps Wiki MCP Server environment.
This tool creates or modifies wiki page content without permanently destroying data. Changes to wiki pages are typically version-controlled and reversible through history/rollback mechanisms, making it a Write operation rather than Destructive.
From the tool's definition Tool description states 'Update content of an existing wiki page or create a new page if it does not exist', indicating reversible creation and modification of wiki page data.
Attacks that exploit this kind of access
Update content of an existing wiki page or create a new page if it does not exist. It is categorised as a Write tool in the Azure DevOps Wiki MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Azure DevOps Wiki MCP Server MCP server in PolicyLayer and add a rule for wiki_update_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 Wiki MCP Server. Nothing to install.
wiki_update_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wiki_update_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 wiki_update_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.
wiki_update_page is provided by the Azure DevOps Wiki MCP Server MCP server (uright/azure-devops-wiki-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 →