observe_tool_complete
v2.1.0 \u2014 Record successful completion. Computes durationMs from observe_tool_start. No-op on unknown callId.
This record as markdown: /tools/danielsimonjr-memory-mcp/observe-tool-complete.md
What observe_tool_complete does on Enhanced Knowledge Graph Memory Server
AI agents use observe_tool_complete to create or update resources in Enhanced Knowledge Graph Memory Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enhanced Knowledge Graph Memory Server environment.
Why observe_tool_complete is rated Medium
This tool records the completion of a tool call, writing timing and status data into the persistent knowledge graph. It is a Write operation (creates/modifies a record), not destructive or financial. Severity is low since it only logs metadata and is a no-op on unknown callIds, limiting blast radius.
From the tool's definition 'Record successful completion' and 'Computes durationMs from observe_tool_start' — writes completion metadata/timing data to the knowledge graph
Attacks that exploit this kind of access
The rule that runs observe_tool_complete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For observe_tool_complete, this is the rule to start with:
observe_tool_complete 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every observe_tool_complete call is checked against it from then on.
Questions about observe_tool_complete
v2.1.0 \u2014 Record successful completion. Computes durationMs from observe_tool_start. No-op on unknown callId. It is categorised as a Write tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for observe_tool_complete: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
observe_tool_complete 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 observe_tool_complete 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 observe_tool_complete. 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.
observe_tool_complete is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue