This record as markdown: /tools/yanhuifair-godot-mcp/read-character-body.md
What read_character_body does on Godot
AI agents call read_character_body 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 |
|---|---|---|---|
name | object | — | CharacterBody node name |
scene_path | string | Yes | Path to .tscn scene |
Parameters from the server's own tool schema.
Why read_character_body is rated Low
This tool retrieves properties of a CharacterBody node in Godot without creating, modifying, deleting, or executing any code. It is a pure data retrieval operation with no side effects, fitting the Read category definition. The blast radius is minimal as it only exposes existing game engine state.
From the tool's definition Tool name 'read_character_body' and description 'Read CharacterBody properties' both explicitly indicate a read-only retrieval operation with no modification or execution.
Attacks that exploit this kind of access
The rule that runs read_character_body 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_character_body, this is the rule to start with:
read_character_body 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_character_body call is checked against it from then on.
Questions about read_character_body
Read CharacterBody properties. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
read_character_body accepts 2 parameters: name, scene_path. Required: 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_character_body: 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_character_body 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_character_body 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_character_body. 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_character_body 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