List source code at current location or specified location, with VS Code integration
AI agents call gdb_list_source to retrieve information from MCP GDB Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays source code during a debugging session. It performs no modifications, deletions, or execution of code—only inspection and presentation of existing code files. This is a read-only operation with minimal blast radius if misused by an AI agent (worst case: leaking source code contents, which is a confidentiality concern but not operationally destructive).
From the tool's definition Tool name 'gdb_list_source' and description 'List source code at current location or specified location' indicate retrieval of source code without modification. The VS Code integration is a display/UI feature, not a side effect.
Documented attack patterns abuse exactly the kind of access gdb_list_source gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP GDB Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gdb_list_source:
{
"version": "1",
"default": "deny",
"tools": {
"gdb_list_source": {}
}
}gdb_list_source 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.
List source code at current location or specified location, with VS Code integration. It is categorised as a Read tool in the MCP GDB Server MCP Server, which means it retrieves data without modifying state.
Register the MCP GDB Server MCP server in PolicyLayer and add a rule for gdb_list_source: 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 GDB Server. Nothing to install.
gdb_list_source 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 gdb_list_source 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 gdb_list_source. 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.
gdb_list_source is provided by the MCP GDB Server MCP server (signal-slot/mcp-gdb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 MCP GDB Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 MCP GDB Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.