AI agents call search_in_project to retrieve information from Godot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Search term (case-insensitive) |
pattern | object | — | File pattern filter (e.g. "*.gd") |
max_results | object | — | Max results (default: 50) |
Parameters from the server's own tool schema.
This tool searches through project files to find text patterns. It is a read-only operation with no side effects—it does not create, modify, delete, or execute code. The blast radius of misuse is minimal; worst case, it leaks knowledge of project structure or sensitive strings, but causes no irreversible changes.
From the tool's definition Tool name 'search_in_project' and description 'Search for text across project files' indicate a query operation that retrieves data without modification.
Attacks that exploit this kind of access
Search for text across project files. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
search_in_project accepts 3 parameters: query, pattern, max_results. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for search_in_project: 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 Godot. Nothing to install.
search_in_project 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_in_project 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_in_project. 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_in_project is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
search_in_project is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →