⭐ PREFERRED OVER Grep: Search for code patterns with regex support. Returns ranked results with minimal context. Better than Grep because it ranks by relevance and provides AI-optimized output. Use for pattern matching and text search.
AI agents call search_code to retrieve information from MCP Context Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only code search utility. It queries and retrieves code based on patterns and text matching, with no side effects or ability to modify, delete, or execute code. The primary function is information retrieval, which is the defining characteristic of the Read category.
From the tool's definition Tool performs 'search for code patterns' and 'returns ranked results' with 'text search' capabilities. No modifications, deletions, or executions are performed.
Documented attack patterns abuse exactly the kind of access search_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Context Manager, and nothing reaches the server without passing your rules. This is the rule we recommend for search_code:
{
"version": "1",
"default": "deny",
"tools": {
"search_code": {}
}
}search_code is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
⭐ PREFERRED OVER Grep: Search for code patterns with regex support. Returns ranked results with minimal context. Better than Grep because it ranks by relevance and provides AI-optimized output. Use for pattern matching and text search. It is categorised as a Read tool in the MCP Context Manager MCP Server, which means it retrieves data without modifying state.
Register the MCP Context Manager 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 Context Manager. 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 Context Manager MCP server (transparentlyok/mcp-context-manager). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Context Manager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 MCP Context Manager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.