AI agents call list_visual_shaders to retrieve information from Godot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | object | — | Subdirectory to search (default: root) |
recursive | object | — | Search recursively |
Parameters from the server's own tool schema.
This tool retrieves or enumerates existing VisualShader graph files in the Godot project without creating, modifying, deleting, or executing anything. It is a pure read operation with minimal risk—listing files cannot harm the project or expose sensitive data in a meaningful way beyond normal file system inspection.
From the tool's definition Tool name 'list_visual_shaders' and description 'List VisualShader graph files' indicate a query/retrieval operation with no modification or side effects.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
List VisualShader graph files. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
list_visual_shaders accepts 2 parameters: path, recursive. 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 list_visual_shaders: 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.
list_visual_shaders 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 list_visual_shaders 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 list_visual_shaders. 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.
list_visual_shaders 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.
list_visual_shaders 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 →