모든 히스토리를 삭제합니다. (주의: 되돌릴 수 없음)
AI agents call history_clear to permanently remove resources in SVG Canvas MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes all history data without the ability to undo the operation. This is a classic destructive action that cannot be reversed. While the blast radius is limited to the local SVG canvas history rather than data persistence layers, the irreversible nature and explicit warning about being unable to undo it places this squarely in the Destructive category.
From the tool's definition Tool description states '모든 히스토리를 삭제합니다. (주의: 되돌릴 수 없음)' which translates to 'Deletes all history. (Warning: cannot be undone)'. The explicit mention of irreversibility and the verb '삭제합니다' (delete) clearly indicate a destructive operation.
Attacks that exploit this kind of access
모든 히스토리를 삭제합니다. (주의: 되돌릴 수 없음). It is categorised as a Destructive tool in the SVG Canvas MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SVG Canvas MCP server in PolicyLayer and add a rule for history_clear: 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 SVG Canvas MCP. Nothing to install.
history_clear 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 history_clear 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 history_clear. 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.
history_clear is provided by the SVG Canvas MCP server (kim62210/svg-canvas-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 →