Low Risk

get_work_memory_versions

메모리의 버전 정보를 조회하고 버전 간 비교를 수행합니다.

How to control get_work_memory_versions ↓

What get_work_memory_versions does on Work Memory MCP Server

AI agents call get_work_memory_versions 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 get_work_memory_versions needs a policy

This tool retrieves and compares version history metadata. It queries existing data without creating, modifying, deleting, executing code, or moving money. The operation is purely informational and has no side effects. Severity is low because version comparison poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'get_work_memory_versions' and description indicating it 'retrieves version information' and 'performs comparison between versions' — these are read/query operations with no modification or deletion.

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

How to control get_work_memory_versions

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

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

get_work_memory_versions 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 get_work_memory_versions

What does the get_work_memory_versions 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 get_work_memory_versions? +

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

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

Can I rate-limit get_work_memory_versions? +

Yes. Add a rate_limit block to the get_work_memory_versions 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 get_work_memory_versions completely? +

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

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