get_node_signals
Get all signals defined on a node type with their argument signatures
This record as markdown: /tools/keeveeg-godot-mcp/get-node-signals.md
What get_node_signals does on Godot
AI agents call get_node_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 |
|---|---|---|---|
type | string | Yes | Node type name (e.g. 'Sprite2D', 'CharacterBody3D') |
Parameters from the server's own tool schema.
Why get_node_signals is rated Low
This tool retrieves and returns information about signals (event definitions) on Godot node types. It is purely informational—reading metadata about signal signatures. There are no side effects, no data creation or modification, no code execution, and no destructive operations. This fits squarely within the Read category as a query/fetch operation.
From the tool's definition Tool name 'get_node_signals' and description 'Get all signals defined on a node type with their argument signatures' indicate a retrieval operation that queries metadata about node signals without modifying any state.
Attacks that exploit this kind of access
The rule that runs get_node_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 get_node_signals, this is the rule to start with:
get_node_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 get_node_signals call is checked against it from then on.
Questions about get_node_signals
Get all signals defined on a node type with their argument signatures. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
get_node_signals accepts 1 parameter: type. Required: type. 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 get_node_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.
get_node_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 get_node_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 get_node_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.
get_node_signals 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