当用户明确要求清空演示数据或恢复 demo 初始状态时调用。
AI agents call reset_demo_data to permanently remove resources in GitBranchMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly clears or overwrites demo data by resetting it to an initial state. While scoped to demo data rather than production data, the action itself is destructive and cannot be undone without re-initialization. The high severity reflects that an inadvertent or malicious call could eliminate user work or state within the demo environment.
From the tool's definition Tool name 'reset_demo_data' and description '当用户明确要求清空演示数据或恢复 demo 初始状态时调用' (When the user explicitly requests to clear demo data or restore demo to initial state, call this) — the phrase '清空演示数据' (clear/empty demo data) directly indicates irreversible…
Attacks that exploit this kind of access
当用户明确要求清空演示数据或恢复 demo 初始状态时调用。. It is categorised as a Destructive tool in the GitBranchMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitBranch MCP server in PolicyLayer and add a rule for reset_demo_data: 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 GitBranchMCP. Nothing to install.
reset_demo_data 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 reset_demo_data 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 reset_demo_data. 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.
reset_demo_data is provided by the GitBranch MCP server (lianggaoyuan/gitbranchmcp). 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 →