divergence guard를 우회하여 한쪽을 강제로 채택합니다.
AI agents call force_sync to permanently remove resources in Remote Memory MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool forcefully overwrites synchronized data by bypassing conflict detection mechanisms. When used on a bidirectional knowledge graph and repository system, it would irreversibly discard one version of entities, relationships, or observations in favor of another, destroying data that cannot be recovered. The deliberate bypass of safety checks (divergence guard) elevates severity to critical.
From the tool's definition Tool description states 'divergence guard를 우회하여 한쪽을 강제로 채택합니다' (bypassing divergence guard to forcefully adopt one side). The term '강제로 채택' (forcefully adopt/enforce) combined with bypassing safeguards indicates irreversible overwrite of data.
Attacks that exploit this kind of access
divergence guard를 우회하여 한쪽을 강제로 채택합니다. It is categorised as a Destructive tool in the Remote Memory MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Remote Memory MCP Server MCP server in PolicyLayer and add a rule for force_sync: 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 Remote Memory MCP Server. Nothing to install.
force_sync 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 force_sync 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 force_sync. 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.
force_sync is provided by the Remote Memory MCP Server MCP server (yeomyujun/remote-memory-mcp-server). 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 →