Low Risk

list_wiki_pages

List pages within an Azure DevOps wiki

How to control list_wiki_pages ↓

AI agents call list_wiki_pages to retrieve information from Azure DevOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves or queries wiki page information with no side effects, fitting squarely into the Read category. The blast radius of misuse is minimal—an AI agent could only enumerate wiki pages it has access to, which poses no security risk. Confidence is high based on explicit 'list' operation and read-only nature of wiki page enumeration.

From the tool's definition Tool name 'list_wiki_pages' and description 'List pages within an Azure DevOps wiki' indicate a retrieval operation that queries and returns wiki page metadata without modifying any data.

Documented attack patterns abuse exactly the kind of access list_wiki_pages gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Azure DevOps MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_wiki_pages:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_wiki_pages": {}
  }
}

list_wiki_pages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Azure DevOps MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_wiki_pages tool do? +

List pages within an Azure DevOps wiki. It is categorised as a Read tool in the Azure DevOps MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_wiki_pages? +

Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for list_wiki_pages: 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 list_wiki_pages? +

list_wiki_pages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_wiki_pages? +

Yes. Add a rate_limit block to the list_wiki_pages 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 list_wiki_pages completely? +

Set action: deny in the PolicyLayer policy for list_wiki_pages. 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 list_wiki_pages? +

list_wiki_pages is provided by the Azure DevOps MCP Server MCP server (tiberriver256/mcp-server-azure-devops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Azure DevOps MCP Server tool call.

Deterministic rules across all 42 Azure DevOps MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

42 Azure DevOps MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.