find_symbol
Locate where GDScript symbols are DECLARED across the project — class_name, inner class, func, signal, enum, const and var. Read-only project index. This is the workspace-symbol answer Godot's language server does not implement (gd_workspace_symbols returns 'unsupported'); for the semantic, posit...
This record as markdown: /tools/breakpoint-mcp/find-symbol.md
What find_symbol does on Breakpoint
AI agents call find_symbol 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 |
|---|---|---|---|
name | string | Yes | Symbol name to look for |
exact | boolean | — | Require an exact name match (default false = substring) |
kinds | array | — | Restrict to these declaration kinds (default: all) |
max_results | integer | — | Cap on returned declarations (default 200) |
Parameters from the server's own tool schema.
Why find_symbol is rated Low
find_symbol performs static code analysis to discover symbol declarations across a project, returning positional metadata. This is a read-only lookup operation analogous to search or index queries. There is no capability to modify, execute, or delete data. The blast radius of misuse is minimal—an AI could only discover symbol locations, which is already visible in the source code itself.
From the tool's definition Tool description explicitly states 'Read-only project index' and 'Locate where GDScript symbols are DECLARED' — a retrieval operation with no side effects. The tool queries symbol locations without modifying code or state.
Attacks that exploit this kind of access
The rule that runs find_symbol 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 find_symbol, this is the rule to start with:
find_symbol 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 find_symbol call is checked against it from then on.
Questions about find_symbol
Locate where GDScript symbols are DECLARED across the project — class_name, inner class, func, signal, enum, const and var. Read-only project index. This is the workspace-symbol answer Godot's language server does not implement (gd_workspace_symbols returns 'unsupported'); for the semantic, position-based lookup on a single build use gd_definition instead. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
find_symbol accepts 4 parameters: name, exact, kinds, max_results. Required: name. 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 find_symbol: 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.
find_symbol 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 find_symbol 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 find_symbol. 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.
find_symbol 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