Search wiki pages by content or title
AI agents call search_wiki_pages to retrieve information from MCP Server for Azure DevOps without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or searches existing wiki page data without side effects. It performs a query operation that returns results but does not create, modify, delete, or execute any code. The low severity reflects minimal blast radius—misuse would only expose wiki content that may already be accessible within the organization.
From the tool's definition Tool name 'search_wiki_pages' and description 'Search wiki pages by content or title' indicate a read-only operation that queries wiki page content without modification, deletion, or execution.
Attacks that exploit this kind of access
Search wiki pages by content or title. It is categorised as a Read tool in the MCP Server for Azure DevOps MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Azure DevOps MCP server in PolicyLayer and add a rule for search_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 MCP Server for Azure DevOps. Nothing to install.
search_wiki_pages 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_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.
Set action: deny in the PolicyLayer policy for search_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.
search_wiki_pages is provided by the MCP Server for Azure DevOps MCP server (sepal7/mcp-ado). 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 →