update_wiki_page · Azure DevOps MCP Server MCP

WHAT IT DOES

What update_wiki_page does on Azure DevOps MCP Server

AI agents use update_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.

WHY IT NEEDS A POLICY

Why update_wiki_page needs a policy

This tool creates or modifies data reversibly—a wiki page can be updated, rolled back, or reverted. It does not delete or permanently destroy content (which would be Destructive), nor does it execute arbitrary code or trigger external operations (Execute).

From the tool's definition Tool name 'update_wiki_page' and description 'Update an existing wiki page' indicate modification of content. The requirement to provide an ETag version parameter ensures this is an update operation, not a destructive delete.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_wiki_page Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_wiki_page": {
      "limits": [
        {
          "counter": "update_wiki_page_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Azure DevOps MCP Server, so you can run agents against it safely.

FAQ

Questions about update_wiki_page

What does the update_wiki_page tool do? +

Update an existing wiki page. Requires the page version (ETag) which can be obtained from get_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.

How do I enforce a policy on update_wiki_page? +

Register the Azure DevOps MCP Server 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. Nothing to install.

What risk level is update_wiki_page? +

update_wiki_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_wiki_page? +

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.

How do I block update_wiki_page completely? +

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.

What MCP server provides update_wiki_page? +

update_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.