로컬 infinite_context_keeper.sqlite의 사용자 데이터 전부 삭제(메모·시맨틱·프로젝트 브레인·컴팩션·Unity 인덱스 등). 되돌릴 수 없음. confirm을 정확히 보내야 실행됩니다.
AI agents call reset_entire_database to permanently remove resources in Infinite Context Keeper — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call reset_entire_database doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Infinite Context Keeper is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
로컬 infinite_context_keeper.sqlite의 사용자 데이터 전부 삭제(메모·시맨틱·프로젝트 브레인·컴팩션·Unity 인덱스 등). 되돌릴 수 없음. confirm을 정확히 보내야 실행됩니다. It is categorised as a Destructive tool in the Infinite Context Keeper MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Infinite Context Keeper MCP server in PolicyLayer and add a rule for reset_entire_database: 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 Infinite Context Keeper. Nothing to install.
reset_entire_database 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_entire_database 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_entire_database. 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_entire_database is provided by the Infinite Context Keeper MCP server (sujkh85/infinite-context-keeper-node). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.