【清理操作】清空当前会话的所有命令历史记录。操作不可逆。
AI agents call clear_command_history to permanently remove resources in LuzzyTool — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently and irreversibly deletes command history data. Although the blast radius is limited to command history rather than critical user data, the irreversible nature of deletion and the fact that it cannot be undone makes this Destructive rather than Write.
From the tool's definition Tool description states '清理操作' (clear operation) and explicitly '操作不可逆' (operation is irreversible). The tool name 'clear_command_history' combined with 'irreversible operation' indicates permanent deletion of command history records.
Attacks that exploit this kind of access
【清理操作】清空当前会话的所有命令历史记录。操作不可逆。. It is categorised as a Destructive tool in the LuzzyTool MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LuzzyTool MCP server in PolicyLayer and add a rule for clear_command_history: 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 LuzzyTool. Nothing to install.
clear_command_history 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 clear_command_history 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 clear_command_history. 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.
clear_command_history is provided by the LuzzyTool MCP server (luzzymeow/luzzytool). 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 →