AI agents call search_work_memory 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 retrieves or queries data from a work memory database based on keywords with no side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch)'. The search operation is non-destructive and does not modify, create, or execute external commands. Low severity because misuse would only expose stored information, not cause irreversible harm.
From the tool's definition Tool name 'search_work_memory' and description indicate 'keyword-based search' in a work memory database. The term '검색' (search) in Korean confirms retrieval without modification.
Documented attack patterns abuse exactly the kind of access search_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 search_work_memory:
{
"version": "1",
"default": "deny",
"tools": {
"search_work_memory": {}
}
}search_work_memory 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 search_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.
search_work_memory 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 search_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 search_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.
search_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.