memory_core_store_memory · IMS MCP Server MCP: Risk & Policy

WHAT IT DOES

What memory_core_store_memory does on IMS MCP Server

AI agents use memory_core_store_memory to create or update resources in IMS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your IMS MCP Server environment.

WHY IT NEEDS A POLICY

Why memory_core_store_memory needs a policy

The tool name 'memory_core_store_memory' clearly indicates it writes/stores data to a memory system. With empty description, confidence is reduced but the naming pattern and server context (IMS with 'memory storage' capability) strongly suggest a Write operation that creates or modifies persistent memory state. This is reversible (memory can be updated/overwritten) rather than destructive, so Write is appropriate.

From the tool's definition Tool name includes 'store_memory' which indicates data persistence or creation operation. Server description mentions 'memory storage' as a core capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_core_store_memory Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_core_store_memory": {
      "limits": [
        {
          "counter": "memory_core_store_memory_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches IMS MCP Server, so you can run agents against it safely.

FAQ

Questions about memory_core_store_memory

What does the memory_core_store_memory tool do? +

memory_core_store_memory. It is categorised as a Write tool in the IMS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_core_store_memory? +

Register the IMS MCP Server MCP server in PolicyLayer and add a rule for memory_core_store_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 IMS MCP Server. Nothing to install.

What risk level is memory_core_store_memory? +

memory_core_store_memory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit memory_core_store_memory? +

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

How do I block memory_core_store_memory completely? +

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

What MCP server provides memory_core_store_memory? +

memory_core_store_memory is provided by the IMS MCP Server MCP server (jdelon02/ims-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.