엔티티에서 특정 관찰 내용을 삭제합니다
AI agents call delete_observations 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 performs irreversible deletion of data (observations) stored in the knowledge graph. While the blast radius is somewhat contained (deleting specific observations rather than entire entities or repositories), deletion operations that cannot be undone are categorized as Destructive.
From the tool's definition Tool name 'delete_observations' combined with description indicating deletion of observation content from entities. The description (in Korean) translates to 'Delete specific observation content from an entity,' which is an irreversible deletion operation.
Attacks that exploit this kind of access
엔티티에서 특정 관찰 내용을 삭제합니다. 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 delete_observations: 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.
delete_observations 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 delete_observations 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 delete_observations. 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.
delete_observations 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 →