Add new observations to existing entities in the knowledge graph
AI agents use add_observations to create or update resources in Knowledge Graph Memory Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Knowledge Graph Memory Server environment.
This tool creates new observations (data entries) within entities, which is a write operation that modifies the knowledge graph. It is reversible (observations can be deleted via sibling delete_observations), so it does not qualify as Destructive.
From the tool's definition Tool description states 'Add new observations to existing entities' — this creates or appends new data to the knowledge graph. The verb 'add' and action of storing observations constitutes a reversible modification of graph state.
Documented attack patterns abuse exactly the kind of access add_observations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Knowledge Graph Memory Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_observations:
{
"version": "1",
"default": "deny",
"tools": {
"add_observations": {
"limits": [
{
"counter": "add_observations_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_observations stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add new observations to existing entities in the knowledge graph. It is categorised as a Write tool in the Knowledge Graph Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Knowledge Graph Memory 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 Knowledge Graph Memory 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 Knowledge Graph Memory Server MCP server (itseasy21/mcp-knowledge-graph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Knowledge Graph Memory Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Knowledge Graph Memory Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.