Find the definition of a symbol by name. More efficient than searching files - instantly jumps to where a function/class/variable is defined
AI agents call definition 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 retrieves metadata about code structure (symbol definitions) without executing code, modifying files, or triggering side effects. It is a navigation/query operation analogous to 'go to definition' features in IDEs, which are read-only intelligence operations.
From the tool's definition Tool description states it 'finds the definition of a symbol' and 'jumps to where a function/class/variable is defined' - pure information retrieval with no modification, creation, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access definition 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 definition:
{
"version": "1",
"default": "deny",
"tools": {
"definition": {}
}
}definition 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 the definition of a symbol by name. More efficient than searching files - instantly jumps to where a function/class/variable is defined. 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 definition: 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.
definition 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 definition 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 definition. 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.
definition 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.