add_working_memory
Create a TTL-based short-term working memory entry scoped to a session. Working memories auto-expire and can be promoted to long-term storage.
This record as markdown: /tools/danielsimonjr-memory-mcp/add-working-memory.md
What add_working_memory does on Enhanced Knowledge Graph Memory Server
AI agents use add_working_memory 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 add_working_memory is rated Medium
This tool creates or stores data (working memory entries) without permanent side effects—entries auto-expire by design and are scoped to sessions. This is a reversible write operation. It does not execute code, delete data irreversibly, move funds, or modify existing records. Severity is low because the data is ephemeral and session-scoped, limiting blast radius if misused.
From the tool's definition Tool name 'add_working_memory' and description 'Create a TTL-based short-term working memory entry' indicate data creation. The tool creates temporary session-scoped memory entries with automatic expiration.
Attacks that exploit this kind of access
The rule that runs add_working_memory 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 add_working_memory, this is the rule to start with:
add_working_memory 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 add_working_memory call is checked against it from then on.
Questions about add_working_memory
Create a TTL-based short-term working memory entry scoped to a session. Working memories auto-expire and can be promoted to long-term storage. 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 add_working_memory: 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.
add_working_memory 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_working_memory 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_working_memory. 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_working_memory 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