AI agents use create_noise_texture 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 |
|---|---|---|---|
path | string | Yes | Output path for NoiseTexture2D .tres |
width | object | — | Texture width |
height | object | — | Texture height |
seamless | object | — | Seamless tiling |
noise_type | object | — |
Parameters from the server's own tool schema.
This tool creates a new texture resource in the Godot project, which is a reversible modification (can be deleted/undone). It does not execute arbitrary code, delete data, or perform financial operations. The medium severity reflects that creating assets could consume project resources or be used to spam texture generation, but the impact is contained to texture assets and reversible.
From the tool's definition Tool creates a NoiseTexture2D asset, which is a new resource/texture object in Godot. The verb 'create' indicates asset generation that modifies the project state by adding a new texture resource.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Create NoiseTexture2D. 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_noise_texture accepts 5 parameters: path, width, height, seamless, noise_type. Required: 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_noise_texture: 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_noise_texture 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_noise_texture 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_noise_texture. 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_noise_texture 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.
create_noise_texture 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 →