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 permanently remove resources in Breakpoint, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Symbol name query |
Parameters from the server's own tool schema.
Why gd_workspace_symbols is rated Critical
An AI agent that decides to call gd_workspace_symbols doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Breakpoint is gone. There is no undo for destructive operations.
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 removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
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 Destructive tool in the Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
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 Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
Across the catalogue