直接执行GDB Machine Interface (MI)命令。 参数: - command: MI命令 (以 - 开头，如 -break-list, -exec-run) - waitForDone (可选): 是否等待完成响应 (默认true) 示例: - gdb_command({command:
AI agents invoke gdb_command to trigger actions in GDB MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool enables execution of arbitrary GDB MI commands, which can trigger external operations with wide-ranging effects depending on arguments: running/stopping target processes, modifying memory, setting breakpoints, and controlling embedded system behavior.
From the tool's definition Tool name 'gdb_command' with description stating it 'directly executes GDB Machine Interface (MI) commands' with parameters accepting arbitrary MI commands (prefixed with '-', such as -break-list, -exec-run).
Attacks that exploit this kind of access
直接执行GDB Machine Interface (MI)命令。 参数: - command: MI命令 (以 - 开头，如 -break-list, -exec-run) - waitForDone (可选): 是否等待完成响应 (默认true) 示例: - gdb_command({command:. It is categorised as a Execute tool in the GDB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GDB MCP Server MCP server in PolicyLayer and add a rule for gdb_command: 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_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gdb_command 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_command. 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_command 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 →