Search through indexed code using text pattern matching.
AI agents call search_code to retrieve information from Ue Codegraph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query operation against a local SQLite database for code analysis purposes. It retrieves information without side effects, matching the Read category definition. Severity is low because misuse would only expose existing source code already in the repository, with no ability to modify or execute code.
From the tool's definition Tool performs 'search through indexed code using text pattern matching' with no modification, deletion, or execution capabilities. Sibling tools like 'find_*', 'get_*', and 'analyze_*' all indicate query/retrieval operations typical of a code analysis server.
Attacks that exploit this kind of access
Search through indexed code using text pattern matching. It is categorised as a Read tool in the Ue Codegraph MCP Server, which means it retrieves data without modifying state.
Register the Ue Codegraph 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 Ue Codegraph. 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 Ue Codegraph MCP server (yomenstyle/ue-codegraph-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 →