Add observations to existing entities
AI agents use mcp_memory_add_observations to create or update resources in MCP Memory Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Memory Server environment.
This tool creates or appends new observation records to existing entities in the knowledge graph, which is a reversible modification operation. It does not execute external code, delete data, or involve financial transactions.
From the tool's definition Tool name includes 'add_observations' which modifies existing entities by appending data to them. Description states it adds observations 'to existing entities', indicating a create/write operation that extends entity records.
Attacks that exploit this kind of access
Add observations to existing entities. It is categorised as a Write tool in the MCP Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Memory Server MCP server in PolicyLayer and add a rule for mcp_memory_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 MCP Memory Server. Nothing to install.
mcp_memory_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 mcp_memory_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 mcp_memory_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.
mcp_memory_add_observations is provided by the MCP Memory Server MCP server (jessefreitas/mcp_memory). 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 →