gd_document_color
List the color literals the language server recognizes in a script — the Color(...) values an editor draws an inline swatch for — with each one
This record as markdown: /tools/godot-breakpoint-mcp/gd-document-color.md
What gd_document_color does on Godot Breakpoint
AI agents call gd_document_color to retrieve information from Godot Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gd_document_color is rated Low
This tool performs a read-only query of a Godot script's color literal metadata. It retrieves information for display (inline swatches in an editor) without side effects, data modification, code execution, or destructive operations. The verb 'list' combined with 'recognize' clearly indicates information retrieval.
From the tool's definition Tool name is 'gd_document_color' and description states it 'List[s] the color literals the language server recognizes in a script' — a query operation that retrieves and returns information about recognized Color(...) values without modifying or executing…
Attacks that exploit this kind of access
The rule that runs gd_document_color safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gd_document_color, this is the rule to start with:
gd_document_color 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 Breakpoint, apply this rule, and every gd_document_color call is checked against it from then on.
Questions about gd_document_color
List the color literals the language server recognizes in a script — the Color(...) values an editor draws an inline swatch for — with each one. It is categorised as a Read tool in the Godot Breakpoint MCP Server, which means it retrieves data without modifying state.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for gd_document_color: 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 Breakpoint. Nothing to install.
gd_document_color 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 gd_document_color 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 gd_document_color. 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.
gd_document_color is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue