batch_get_properties
🔴 Game must be running. Get multiple properties from multiple nodes in one call
This record as markdown: /tools/keeveeg-godot-mcp/batch-get-properties.md
What batch_get_properties does on Godot
AI agents call batch_get_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 |
|---|---|---|---|
paths | array | Yes | List of node paths to query |
properties | array | Yes | Property names to read from each node |
Parameters from the server's own tool schema.
Why batch_get_properties is rated Low
This tool retrieves property values from game nodes without creating, modifying, or deleting any state. It is a read-only operation that has no side effects on the game state. Severity is low because reading properties cannot cause harm even if misused by an agent.
From the tool's definition Tool name 'batch_get_properties' and description 'Get multiple properties from multiple nodes' indicates retrieval of data with no modifications. The 🔴 indicator notes a runtime requirement but does not change the operation's nature as a query.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_get_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 batch_get_properties, this is the rule to start with:
batch_get_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 batch_get_properties call is checked against it from then on.
Questions about batch_get_properties
🔴 Game must be running. Get multiple properties from multiple nodes in one call. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
batch_get_properties accepts 2 parameters: paths, properties. Required: paths, properties. 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 batch_get_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.
batch_get_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 batch_get_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 batch_get_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.
batch_get_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