Edit an existing wiki page
AI agents use edit_wiki_page to create or update resources in azure-devops MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your azure-devops MCP Server environment.
Editing a wiki page creates or modifies data in a reversible way (edits can be undone via version history in Azure DevOps). This is characteristic of Write operations. Severity is medium because unauthorized wiki edits could spread misinformation or corrupt documentation, affecting team knowledge and project clarity, but the impact is typically contained to documentation and reversible.
From the tool's definition Tool name is 'edit_wiki_page' with description 'Edit an existing wiki page' — this modifies existing data (wiki content) in a reversible manner.
Attacks that exploit this kind of access
Edit an existing wiki page. It is categorised as a Write tool in the azure-devops MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the azure-devops MCP Server MCP server in PolicyLayer and add a rule for edit_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.
edit_wiki_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 edit_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 edit_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.
edit_wiki_page is provided by the azure-devops MCP Server MCP server (mmruesch12/azdo-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 →