Low Risk

list_work_memories

저장된 워크 메모리 목록을 조회합니다. 다양한 필터링과 정렬 옵션을 제공합니다.

How to control list_work_memories ↓

What list_work_memories does on Work Memory MCP Server

AI agents call list_work_memories 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.

Low Risk

Why list_work_memories needs a policy

This tool performs a read-only operation—querying and listing existing data with filter and sort capabilities. It has no side effects, does not modify state, and presents minimal risk if misused by an AI agent (worst case: information disclosure of already-stored work memories). Classified as Read with low severity.

From the tool's definition Tool description indicates 'list_work_memories' retrieves/queries saved work memories with filtering and sorting options ('저장된 워크 메모리 목록을 조회합니다' = 'retrieves list of saved work memories'). No modification, deletion, or execution described.

Documented attack patterns abuse exactly the kind of access list_work_memories gives an agent:

How to control list_work_memories

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 list_work_memories:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_work_memories": {}
  }
}

list_work_memories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Work Memory MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_work_memories

What does the list_work_memories tool do? +

저장된 워크 메모리 목록을 조회합니다. 다양한 필터링과 정렬 옵션을 제공합니다. It is categorised as a Read tool in the Work Memory MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_work_memories? +

Register the Work Memory MCP Server MCP server in PolicyLayer and add a rule for list_work_memories: 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.

What risk level is list_work_memories? +

list_work_memories is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_work_memories? +

Yes. Add a rate_limit block to the list_work_memories 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.

How do I block list_work_memories completely? +

Set action: deny in the PolicyLayer policy for list_work_memories. 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.

What MCP server provides list_work_memories? +

list_work_memories 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.

Enforce policy on every Work Memory MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.