editor_get_class_doc
Open Godot documentation for a class in browser.
This record as markdown: /tools/yanhuifair-godot-mcp/editor-get-class-doc.md
What editor_get_class_doc does on Godot
AI agents invoke editor_get_class_doc to trigger actions in Godot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
class | string | Yes |
Parameters from the server's own tool schema.
Why editor_get_class_doc is rated High
This tool triggers an external operation — opening a browser — rather than simply returning data. Launching a browser process is an Execute-category action since it depends on the argument (the class name) and causes an external side effect beyond the MCP server itself.
From the tool's definition Open Godot documentation for a class in browser
Attacks that exploit this kind of access
The rule that runs editor_get_class_doc 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_get_class_doc, this is the rule to start with:
editor_get_class_doc stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_get_class_doc call is checked against it from then on.
Questions about editor_get_class_doc
Open Godot documentation for a class in browser. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
editor_get_class_doc accepts 1 parameter: class. Required: class. 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_get_class_doc: 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_get_class_doc is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the editor_get_class_doc 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_get_class_doc. 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_get_class_doc 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.
Across the catalogue