AI agents call terminate to permanently remove resources in Dap — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Terminating a debugging session is an irreversible action that ends the running process and destroys the session state. It cannot be undone — the debug session, any in-memory state, and the running program are permanently stopped. This qualifies as Destructive with high severity since misuse would abruptly kill a running debug session and potentially the target process.
From the tool's definition Terminate the current debugging session.
Documented attack patterns abuse exactly the kind of access terminate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dap, and nothing reaches the server without passing your rules. This is the rule we recommend for terminate:
{
"version": "1",
"default": "deny",
"hide": [
"terminate"
]
}terminate disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Terminate the current debugging session. It is categorised as a Destructive tool in the Dap MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dap MCP server in PolicyLayer and add a rule for terminate: 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 Dap. Nothing to install.
terminate is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the terminate 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 terminate. 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.
terminate is provided by the Dap MCP server (kashuncheng/dap_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dap, 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.
14 Dap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.