기존 엔티티에 관찰 내용을 추가합니다
AI agents use add_observations to create or update resources in Remote Memory MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remote Memory MCP Server environment.
The tool creates or modifies data (observations) in a reversible manner without deleting or destroying information. It does not execute code, move money, or perform irreversible operations. The presence of sibling destructive tools (delete_entities, delete_observations, delete_relations, force_sync) confirms this tool's write-only nature.
From the tool's definition Tool description states the tool 'adds observations to existing entities' (기존 엔티티에 관찰 내용을 추가합니다). This is a create/modify operation on data within the knowledge graph.
Attacks that exploit this kind of access
기존 엔티티에 관찰 내용을 추가합니다. It is categorised as a Write tool in the Remote Memory MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remote Memory MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_observations is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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 →