gd_workspace_symbols
Search symbols across the whole project by name. Note: Godot's GDScript language server does not implement LSP 'workspace/symbol' (observed through 4.7), so on those builds this returns a clear 'unsupported' error rather than results — use gd_document_symbols for per-file symbols.
This record as markdown: /tools/breakpoint-mcp/gd-workspace-symbols.md
What gd_workspace_symbols does on Breakpoint
AI agents call gd_workspace_symbols 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 |
|---|---|---|---|
query | string | Yes | Symbol name query |
Parameters from the server's own tool schema.
Why gd_workspace_symbols is rated Low
This tool only searches/queries symbols in a Godot project workspace. It retrieves information without modifying, creating, or deleting anything. Pure read operation with low blast radius.
From the tool's definition Search symbols across the whole project by name
Attacks that exploit this kind of access
The rule that runs gd_workspace_symbols 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_workspace_symbols, this is the rule to start with:
gd_workspace_symbols 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_workspace_symbols call is checked against it from then on.
Questions about gd_workspace_symbols
Search symbols across the whole project by name. Note: Godot's GDScript language server does not implement LSP 'workspace/symbol' (observed through 4.7), so on those builds this returns a clear 'unsupported' error rather than results — use gd_document_symbols for per-file symbols. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
gd_workspace_symbols accepts 1 parameter: query. Required: query. 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_workspace_symbols: 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_workspace_symbols 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_workspace_symbols 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_workspace_symbols. 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_workspace_symbols 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