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's source range, its RGBA components (floats 0..1) and a convenience #RRGGBBAA hex. Read-only. Godot's GDScript language server advertises colorProvider; ...
This record as markdown: /tools/breakpoint-mcp/gd-document-color.md
What gd_document_color does on Breakpoint
AI agents call gd_document_color to retrieve information from Breakpoint 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 |
|---|---|---|---|
path | string | Yes | Script path (res://..., absolute, or project-relative) |
Parameters from the server's own tool schema.
Why gd_document_color is rated Low
This tool retrieves metadata about color definitions in a GDScript document for display purposes (inline swatches in an editor). It has no side effects, cannot modify or delete data, and is explicitly documented as read-only. The highest severity impact would be information disclosure of color values already present in the script, which is benign.
From the tool's definition Tool performs 'List the color literals' and is explicitly marked 'Read-only'. Returns source ranges, RGBA components, and hex values without modifying any state.
Risk signalsAccepts file system path (path)
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 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 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's source range, its RGBA components (floats 0..1) and a convenience #RRGGBBAA hex. Read-only. Godot's GDScript language server advertises colorProvider; feature-detected with a -32601 belt-and-suspenders (advertised ≠ implemented — the D7 lesson). It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
gd_document_color accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the 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 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 Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue