This record as markdown: /tools/yanhuifair-godot-mcp/editor-get-class-signals.md
What editor_get_class_signals does on Godot
AI agents call editor_get_class_signals 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 |
|---|---|---|---|
class | string | Yes |
Parameters from the server's own tool schema.
Why editor_get_class_signals is rated Low
This tool retrieves information about class signals from the Godot engine metadata. It performs a query operation that inspects and returns data without modifying, creating, deleting, or executing anything. No code is executed, no data is altered, and there are no irreversible consequences. This is a straightforward introspection/reflection capability typical of Read category tools.
From the tool's definition Tool name 'editor_get_class_signals' and description 'List all signals of a Godot class' indicate retrieval/query of metadata with no side effects. The verb 'get' and action 'list' are characteristic of read-only operations.
Attacks that exploit this kind of access
The rule that runs editor_get_class_signals 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_signals, this is the rule to start with:
editor_get_class_signals 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_get_class_signals call is checked against it from then on.
Questions about editor_get_class_signals
List all signals of a Godot class. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
editor_get_class_signals 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_signals: 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_signals 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_get_class_signals 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_signals. 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_signals 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