get_shader_node_defaults
Get default ports and parameters for a specific VisualShader node type.
This record as markdown: /tools/yanhuifair-godot-mcp/get-shader-node-defaults.md
What get_shader_node_defaults does on Godot
AI agents call get_shader_node_defaults 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 |
|---|---|---|---|
node_type | string | Yes | Node type shorthand to inspect |
Parameters from the server's own tool schema.
Why get_shader_node_defaults is rated Low
This tool queries and returns default configuration metadata for VisualShader nodes. It performs no modifications, deletions, code execution, or financial operations. It simply retrieves and presents existing default parameters, making it a straightforward Read operation with low severity as misuse would only return irrelevant shader data without impacting the system.
From the tool's definition Tool name 'get_shader_node_defaults' and description 'Get default ports and parameters' indicate a retrieval operation with no side effects. The verb 'Get' and the passive nature of retrieving default configuration data confirm this is a read-only query.
Attacks that exploit this kind of access
The rule that runs get_shader_node_defaults 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 get_shader_node_defaults, this is the rule to start with:
get_shader_node_defaults 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 get_shader_node_defaults call is checked against it from then on.
Questions about get_shader_node_defaults
Get default ports and parameters for a specific VisualShader node type. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
get_shader_node_defaults accepts 1 parameter: node_type. Required: node_type. 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 get_shader_node_defaults: 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.
get_shader_node_defaults 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 get_shader_node_defaults 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 get_shader_node_defaults. 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.
get_shader_node_defaults 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