Add new observations to existing entities in the knowledge graph
AI agents use add_observations to create or update resources in Neo4j MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neo4j MCP Server environment.
This tool creates or modifies data by appending observations to entities in the Neo4j graph. While the operation is reversible (observations can be removed via delete_observations), it changes the state of the knowledge graph. The medium severity reflects that misuse could corrupt data integrity, but the effect is not irreversible like deletion, nor does it execute arbitrary code or affect finances.
From the tool's definition Tool name 'add_observations' combined with description 'Add new observations to existing entities' indicates creation and modification of data.
Attacks that exploit this kind of access
Add new observations to existing entities in the knowledge graph. It is categorised as a Write tool in the Neo4j MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Neo4j 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 Neo4j 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 Neo4j MCP Server MCP server (rebots-online/mcp-neo4j). 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 →