Add new observations to existing entities in the knowledge graph
AI agents use add_observations to create or update resources in Server Sequential Thinking — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Server Sequential Thinking environment.
This tool creates or appends new observations to a knowledge graph—a reversible modification operation. It does not execute arbitrary code, delete data irreversibly, move money, or retrieve data (though it may create new entries). The impact is limited to the knowledge graph's observation layer, with no external side effects.
From the tool's definition Tool name 'add_observations' and description 'Add new observations to existing entities in the knowledge graph' indicate creation of new data entries within an existing knowledge structure.
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 Server Sequential Thinking MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Server Sequential Thinking 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 Server Sequential Thinking. 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 Server Sequential Thinking MCP server (@modelcontextprotocol/server-sequential-thinking). 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 →