create_test_character
Create a test character in the scene at a specified position
This record as markdown: /tools/keeveeg-godot-mcp/create-test-character.md
What create_test_character does on Godot
AI agents use create_test_character to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
position | array | — | World position [x, y, z] |
scene_path | string | Yes | Path to the character scene to instantiate |
Parameters from the server's own tool schema.
Why create_test_character is rated Medium
This tool creates a new scene object (a test character), which is a reversible write operation. It modifies the scene state by adding content, but does not execute arbitrary code, delete data, or cause financial impact. The blast radius is medium because an agent could spam character creation or place characters in unintended locations, but changes are easily undone in the editor.
From the tool's definition Tool name is 'create_test_character' and description states 'Create a test character in the scene at a specified position' — explicitly creates/adds an object to the Godot scene.
Attacks that exploit this kind of access
The rule that runs create_test_character 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 create_test_character, this is the rule to start with:
create_test_character stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_test_character call is checked against it from then on.
Questions about create_test_character
Create a test character in the scene at a specified position. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_test_character accepts 2 parameters: position, 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 create_test_character: 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.
create_test_character is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_test_character 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 create_test_character. 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.
create_test_character 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