get_game_node_properties
🔴 Game must be running. Get all properties of a node in the running game
This record as markdown: /tools/keeveeg-godot-mcp/get-game-node-properties.md
What get_game_node_properties does on Godot
AI agents call get_game_node_properties 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 |
|---|---|---|---|
path | string | Yes | Node path in the game tree |
properties | array | — | Specific property names to return (defaults to common properties) |
Parameters from the server's own tool schema.
Why get_game_node_properties is rated Low
This tool queries and retrieves properties from an active game node, which is a read-only operation. It has no side effects, does not execute code or commands, does not modify data, and does not delete or move resources. The 'get' prefix and 'Get' verb in the description confirm read semantics. Even though it requires the game to be running, it only observes state rather than changing it.
From the tool's definition Tool name 'get_game_node_properties' and description 'Get all properties of a node in the running game' indicate data retrieval with no modification or execution capability.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs get_game_node_properties 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_game_node_properties, this is the rule to start with:
get_game_node_properties 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_game_node_properties call is checked against it from then on.
Questions about get_game_node_properties
🔴 Game must be running. Get all properties of a node in the running game. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
get_game_node_properties accepts 2 parameters: path, properties. Required: path. 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_game_node_properties: 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_game_node_properties 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_game_node_properties 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_game_node_properties. 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_game_node_properties 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