This record as markdown: /tools/yanhuifair-godot-mcp/search-in-scripts.md
What search_in_scripts does on Godot
AI agents call search_in_scripts 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 |
|---|---|---|---|
type | object | — | Script type filter |
query | string | Yes | Search term (function name, variable, keyword) |
max_results | object | — | Max results |
Parameters from the server's own tool schema.
Why search_in_scripts is rated Low
This tool retrieves or queries data from scripts without side effects. Searching through scripts to find patterns or functions is a read-only operation that does not create, modify, delete, or execute code. No irreversible changes or code execution occur.
From the tool's definition Tool name is 'search_in_scripts' and description states 'Search in scripts with function context' — the verb 'search' combined with 'with function context' indicates querying/reading script content, not modifying or executing.
Attacks that exploit this kind of access
The rule that runs search_in_scripts 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_scripts, this is the rule to start with:
search_in_scripts 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_scripts call is checked against it from then on.
Questions about search_in_scripts
Search in scripts with function context. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
search_in_scripts accepts 3 parameters: type, query, 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_scripts: 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_scripts 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_scripts 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_scripts. 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_scripts 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue