Change the current debugging frame to the specified frame ID.
AI agents invoke change_frame to trigger actions in Dap. 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 modifies the active state of a debugging session by switching the current call stack frame. It's an operational control action that affects the debugger's execution context and subsequent operations like evaluate or step. It doesn't read data, write persistent data, or destroy anything, but it does trigger a state change in an external system (the debug adapter), placing it in the Execute category.
From the tool's definition Change the current debugging frame to the specified frame ID
Documented attack patterns abuse exactly the kind of access change_frame 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 change_frame:
{
"version": "1",
"default": "deny",
"tools": {
"change_frame": {
"limits": [
{
"counter": "change_frame_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}change_frame stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Change the current debugging frame to the specified frame ID. It is categorised as a Execute tool in the Dap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Dap MCP server in PolicyLayer and add a rule for change_frame: 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.
change_frame 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 change_frame 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 change_frame. 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.
change_frame 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.