ims_store_memory · IMS MCP Server MCP: Risk & Policy

WHAT IT DOES

What ims_store_memory does on IMS MCP Server

AI agents use ims_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 ims_store_memory needs a policy

The tool stores memory data in an IMS backend, which is a write operation that creates or modifies data. The empty description reduces confidence slightly, but the name and server context clearly indicate memory persistence. Severity is medium because stored memory could influence agent decision-making, but the impact is reversible (memory can be updated or cleared) and depends on what data is stored.

From the tool's definition Tool name 'ims_store_memory' indicates data storage/persistence. Server description mentions 'memory storage' and 'maintain long-term memory across sessions', confirming a write operation that creates or modifies persistent data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ims_store_memory Rate-limited

ims_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": {
    "ims_store_memory": {
      "limits": [
        {
          "counter": "ims_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 ims_store_memory

What does the ims_store_memory tool do? +

ims_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 ims_store_memory? +

Register the IMS MCP Server MCP server in PolicyLayer and add a rule for ims_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 ims_store_memory? +

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

Can I rate-limit ims_store_memory? +

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

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

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