store_memory · Heimdall MCP Server MCP: Risk & Policy

WHAT IT DOES

What store_memory does on Heimdall MCP Server

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

WHY IT NEEDS A POLICY

Why store_memory needs a policy

This tool writes data to a persistent memory store. It creates new records that persist across sessions. While reversible (other tools like delete_memory exist), it modifies the persistent state of the memory system. Misuse could lead to storing incorrect or malicious context that influences future AI behavior, hence medium severity.

From the tool's definition 'Store new experiences or knowledge in cognitive memory for future recall' — creates/writes new memory entries persistently

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

store_memory Rate-limited

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": {
    "store_memory": {
      "limits": [
        {
          "counter": "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 Heimdall MCP Server, so you can run agents against it safely.

FAQ

Questions about store_memory

What does the store_memory tool do? +

Store new experiences or knowledge in cognitive memory for future recall. It is categorised as a Write tool in the Heimdall 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 store_memory? +

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

What risk level is store_memory? +

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

Can I rate-limit store_memory? +

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

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

store_memory is provided by the Heimdall MCP Server MCP server (lcbcfoo/heimdall-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

store_memory is one line of Heimdall MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →