AI agents call get_work_memory_history to retrieve information from Work Memory MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical information about changes to work memories. It retrieves data without creating, modifying, deleting, or executing any operations. The action is purely observational and read-only, fitting the 'Read' category. Severity is low as access to historical metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_work_memory_history' and description '메모리의 변경 이력을 조회합니다' (translates to 'Retrieve the change history of memory') indicates a retrieval/query operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access get_work_memory_history 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 get_work_memory_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_work_memory_history": {}
}
}get_work_memory_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
메모리의 변경 이력을 조회합니다. It is categorised as a Read tool in the Work Memory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Work Memory MCP Server MCP server in PolicyLayer and add a rule for get_work_memory_history: 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.
get_work_memory_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_work_memory_history 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 get_work_memory_history. 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.
get_work_memory_history 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.