Search for patterns across the source project at: ${resolvedSourcePath}. Supports both literal text and regex patterns. Returns matching file paths, line numbers, and content.
AI agents call search_code to retrieve information from Cross-Project MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs pattern matching and retrieval of source code information without modifying data, executing commands, or triggering external operations. It is purely informational—comparable to grep or code search utilities. The low severity reflects that misuse would only expose existing code/information, not cause destructive or financial harm.
From the tool's definition Tool description states it "Search[es] for patterns across the source project" and "Returns matching file paths, line numbers, and content." The verb "search" combined with "returns" indicates data retrieval with no modification or execution of code.
Attacks that exploit this kind of access
Search for patterns across the source project at: ${resolvedSourcePath}. Supports both literal text and regex patterns. Returns matching file paths, line numbers, and content. It is categorised as a Read tool in the Cross-Project MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cross-Project MCP Server 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 Cross-Project MCP Server. 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 Cross-Project MCP Server MCP server (sweetsrepo/cross-project-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 →