AI agents use update_wiki_page to create or update resources in Azure DevOps MCP Server for Cline — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure DevOps MCP Server for Cline environment.
This tool creates or modifies wiki pages, which are reversible changes to documentation. While wiki updates can affect team knowledge and processes, the impact is editable and recoverable (prior versions can typically be restored). This is Write rather than Destructive because wiki page modifications do not irreversibly delete data.
From the tool's definition Tool description states 'Create or update a wiki page' — directly modifies wiki content. The verb 'update' and 'create' are Write operations.
Documented attack patterns abuse exactly the kind of access update_wiki_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Azure DevOps MCP Server for Cline, and nothing reaches the server without passing your rules. This is the rule we recommend for update_wiki_page:
{
"version": "1",
"default": "deny",
"tools": {
"update_wiki_page": {
"limits": [
{
"counter": "update_wiki_page_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_wiki_page stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create or update a wiki page. It is categorised as a Write tool in the Azure DevOps MCP Server for Cline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Azure DevOps MCP Server for Cline MCP server in PolicyLayer and add a rule for update_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 for Cline. Nothing to install.
update_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 update_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 update_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.
update_wiki_page is provided by the Azure DevOps MCP Server for Cline MCP server (stefanskiasan/azure-devops-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Azure DevOps MCP Server for Cline tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Azure DevOps MCP Server for Cline tools catalogued and risk-classified — across an index of 42,500+ MCP servers.