read_spring_arm
List SpringArm3D nodes with spring length and collision settings.
This record as markdown: /tools/yanhuifair-godot-mcp/read-spring-arm.md
What read_spring_arm does on Godot
AI agents call read_spring_arm 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 |
|---|---|---|---|
scene_path | object | — |
Parameters from the server's own tool schema.
Why read_spring_arm is rated Low
This tool retrieves and displays configuration information about SpringArm3D nodes in the Godot scene hierarchy. It performs no modifications, deletions, or side effects—it purely queries and reports existing node state. This is characteristic of a Read category tool with low security risk.
From the tool's definition Tool name 'read_spring_arm' and description 'List SpringArm3D nodes' indicates data retrieval with no modification. The verb 'List' and context of reading node properties (spring length, collision settings) confirms a query-only operation.
Attacks that exploit this kind of access
The rule that runs read_spring_arm 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 read_spring_arm, this is the rule to start with:
read_spring_arm 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 read_spring_arm call is checked against it from then on.
Questions about read_spring_arm
List SpringArm3D nodes with spring length and collision settings. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
read_spring_arm accepts 1 parameter: scene_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 read_spring_arm: 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.
read_spring_arm 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 read_spring_arm 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 read_spring_arm. 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.
read_spring_arm 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