gd_references
Find all references to the symbol at a position.
This record as markdown: /tools/breakpoint-mcp/gd-references.md
What gd_references does on Breakpoint
AI agents call gd_references 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 |
|---|---|---|---|
line | integer | Yes | 0-based line |
path | string | Yes | Script path (res://..., absolute, or project-relative) |
character | integer | Yes | 0-based character |
include_declaration | boolean | — | Include the declaration (default true) |
Parameters from the server's own tool schema.
Why gd_references is rated Low
This tool queries/searches for references to a symbol in code. It only reads and retrieves information without modifying any data, making it a straightforward Read operation with minimal blast radius.
From the tool's definition Find all references to the symbol at a position
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs gd_references 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_references, this is the rule to start with:
gd_references 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_references call is checked against it from then on.
Questions about gd_references
Find all references to the symbol at a position. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
gd_references accepts 4 parameters: line, path, character, include_declaration. Required: line, path, character. 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_references: 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_references 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_references 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_references. 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_references 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