This record as markdown: /tools/keeveeg-godot-mcp/search-in-files.md
What search_in_files does on Godot
AI agents call search_in_files to retrieve information from Godot without modifying anything. It is 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 query |
file_pattern | string | — | File pattern to search in (e.g. '*.gd') |
Parameters from the server's own tool schema.
Why search_in_files is rated Low
This tool performs a search operation across project files, which is a read-only retrieval operation. It does not modify, execute, delete, or create any data. The blast radius is minimal as the tool can only return matching text results. Even in the context of a Godot MCP server where other tools perform modifications, this specific tool is clearly categorized as a Read operation.
From the tool's definition Tool name is 'search_in_files' and description states 'Search for text across project files' — both indicate querying/retrieving data with no side effects.
Attacks that exploit this kind of access
The rule that runs search_in_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_in_files, this is the rule to start with:
search_in_files is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every search_in_files call is checked against it from then on.
Questions about search_in_files
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_files accepts 2 parameters: query, file_pattern. 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_files: 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_files 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_files 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_files. 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_files is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue