Search across wiki content using Azure DevOps Search API
AI agents call search_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 queries and retrieves wiki content matching search criteria. It is a read operation that does not create, modify, delete, execute code, or commit financial actions. The presence of sibling tools like wiki_update_page and wiki_get_page confirms that search_wiki is distinctly the retrieval/query function.
From the tool's definition The tool is named 'search_wiki' and described as 'Search across wiki content using Azure DevOps Search API'. The verb 'search' and phrase 'across wiki content' indicate a read-only retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Search across wiki content using Azure DevOps Search API. 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 search_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.
search_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 search_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 search_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.
search_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.
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 →