Search code across repositories
AI agents call search_code 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.
The tool retrieves and searches code content without creating, modifying, or deleting data. It has no side effects beyond returning search results. This is a classic Read category tool. Severity is low because searching code poses minimal risk—it only exposes information already in the repository without triggering builds, deployments, or other operations.
From the tool's definition Tool name 'search_code' and description 'Search code across repositories' indicate a read-only query operation with no data modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search code across repositories. 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_code: 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_code 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_code 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_code. 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_code 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 →