기존 메모리의 내용을 업데이트합니다. 할일 완료 시 content(작업요약)와 result_content(결과물)를 함께 업데이트하세요.
AI agents use update_work_memory to create or update resources in Work Memory MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Work Memory MCP Server environment.
This tool creates or modifies data reversibly—updates to work memory records can be undone by subsequent updates or deletion. It does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is medium because corrupted or malicious updates could pollute the work memory system and mislead subsequent AI operations, but the changes remain editable and recoverable.
From the tool's definition Tool name and description indicate 'update_work_memory' modifies existing memory records. Description states it updates 'content' and 'result_content' fields when tasks are completed, which are reversible modifications to stored data.
Documented attack patterns abuse exactly the kind of access update_work_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Work Memory MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_work_memory:
{
"version": "1",
"default": "deny",
"tools": {
"update_work_memory": {
"limits": [
{
"counter": "update_work_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_work_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.
Free to start. No card required.
기존 메모리의 내용을 업데이트합니다. 할일 완료 시 content(작업요약)와 result_content(결과물)를 함께 업데이트하세요. It is categorised as a Write tool in the Work Memory MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Work Memory MCP Server MCP server in PolicyLayer and add a rule for update_work_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 Work Memory MCP Server. Nothing to install.
update_work_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 update_work_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 update_work_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.
update_work_memory is provided by the Work Memory MCP Server MCP server (moontmsai/work-memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Work Memory MCP 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.
24 Work Memory MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.