Regex/grep search over symbol name and doc_comment columns only (NOT function bodies — bodies are never stored). Uses Postgres ~ operator.
AI agents call code.search_text to retrieve information from Lore Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data without side effects. It searches metadata (symbol names and documentation comments) in a read-only manner using regex patterns. There is no capability to modify, delete, execute code, or trigger external operations. The explicit note that function bodies are not stored and only searchable columns are symbol names and doc comments confirms this is purely informational retrieval.
From the tool's definition Tool performs 'Regex/grep search' over 'symbol name and doc_comment columns only' with 'NOT function bodies'. Uses read-only Postgres ~ operator. No mutation, deletion, or execution capability described.
Attacks that exploit this kind of access
Regex/grep search over symbol name and doc_comment columns only (NOT function bodies — bodies are never stored). Uses Postgres ~ operator. It is categorised as a Read tool in the Lore Context MCP Server, which means it retrieves data without modifying state.
Register the Lore Context MCP server in PolicyLayer and add a rule for code.search_text: 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 Lore Context. Nothing to install.
code.search_text 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 code.search_text 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 code.search_text. 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.
code.search_text is provided by the Lore Context MCP server (Lore-Context/lore-context). 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 →