列出调试程序的所有源文件。
AI agents call gdb_list_source_files to retrieve information from GDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only—it queries and returns information about source files without side effects, state changes, or execution of code. It falls clearly into the Read category. Severity is low because exposing a list of source files presents minimal risk; an agent could learn about the program structure but cannot execute code, modify systems, or cause data loss through this operation alone.
From the tool's definition Tool name 'gdb_list_source_files' and description indicate it lists source files of a debugged program. The description translates to 'Lists all source files of the debugging program.' This is a read-only operation that retrieves metadata about available…
Attacks that exploit this kind of access
列出调试程序的所有源文件。. It is categorised as a Read tool in the GDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GDB MCP Server MCP server in PolicyLayer and add a rule for gdb_list_source_files: 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 GDB MCP Server. Nothing to install.
gdb_list_source_files 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_files 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_files. 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_files is provided by the GDB MCP Server MCP server (zjm1060/gdb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →