Find all references to a symbol by name. Superior to grep - finds semantic references including imports, type usage, and renamed variables
AI agents call references to retrieve information from MCP Server for VS Code without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static code analysis to locate symbol references within a codebase. It reads and queries code structure to return matching results, with no side effects, code execution, or data modification. It is a straightforward Read operation—gathering intelligence about code relationships.
From the tool's definition Tool name 'references' and description states it 'Find all references to a symbol by name' - a query operation that retrieves data about code symbols without modifying, deleting, or executing code.
Documented attack patterns abuse exactly the kind of access references gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for VS Code, and nothing reaches the server without passing your rules. This is the rule we recommend for references:
{
"version": "1",
"default": "deny",
"tools": {
"references": {}
}
}references is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find all references to a symbol by name. Superior to grep - finds semantic references including imports, type usage, and renamed variables. It is categorised as a Read tool in the MCP Server for VS Code MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for VS Code MCP server in PolicyLayer and add a rule for 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 MCP Server for VS Code. Nothing to install.
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 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 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.
references is provided by the MCP Server for VS Code MCP server (malvex/mcp-server-vscode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for VS Code, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 MCP Server for VS Code tools catalogued and risk-classified — across an index of 43,000+ MCP servers.