List all wikis in a project
AI agents call list_wiki to retrieve information from Azure DevOps Wiki MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates wikis within a project namespace. It is purely informational with no side effects. There is no data modification, deletion, code execution, or financial impact. The blast radius of misuse is minimal—an agent can only discover what wikis exist, not alter them.
From the tool's definition Tool name is 'list_wiki' and description states 'List all wikis in a project' — a query operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
List all wikis in a project. It is categorised as a Read tool in the Azure DevOps Wiki MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure DevOps Wiki MCP Server MCP server in PolicyLayer and add a rule for list_wiki: 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.
list_wiki is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_wiki 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 list_wiki. 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.
list_wiki 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.
list_wiki is one line of Azure DevOps Wiki MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →