AI agents use load_sprite 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 |
|---|---|---|---|
node_path | string | Yes | Node path (Sprite2D or TextureRect) |
scene_path | string | Yes | Path to .tscn file |
texture_path | string | Yes | Texture resource path (e.g. "res://icon.svg") |
Parameters from the server's own tool schema.
This tool modifies a node's state by assigning a texture resource to it. It creates/updates a property on an existing scene node, which is a reversible write operation. Misuse could corrupt sprite references in a scene, but effects are localized and reversible.
From the tool's definition Load a texture onto a Sprite2D node
Attacks that exploit this kind of access
Load a texture onto a Sprite2D node. 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.
load_sprite accepts 3 parameters: node_path, scene_path, texture_path. Required: node_path, scene_path, texture_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 load_sprite: 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.
load_sprite 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 load_sprite 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 load_sprite. 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.
load_sprite 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.
load_sprite is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →