This record as markdown: /tools/yanhuifair-godot-mcp/editor-search-help.md
What editor_search_help does on Godot
AI agents call editor_search_help 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 |
Parameters from the server's own tool schema.
Why editor_search_help is rated Low
This tool performs a search operation on Godot documentation—a read-only retrieval of informational content. It has no side effects on the project, engine, or any data structures. The browser action is purely for display/navigation purposes, not for triggering external operations or modifying state.
From the tool's definition Tool name 'editor_search_help' and description 'Search Godot documentation in browser' indicate a query operation that retrieves documentation information without modifying any game state, project files, or engine configuration.
Attacks that exploit this kind of access
The rule that runs editor_search_help 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 editor_search_help, this is the rule to start with:
editor_search_help 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 editor_search_help call is checked against it from then on.
Questions about editor_search_help
Search Godot documentation in browser. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
editor_search_help accepts 1 parameter: query. 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 editor_search_help: 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.
editor_search_help 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 editor_search_help 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 editor_search_help. 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.
editor_search_help 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