memory.store · Sylex Memory MCP: Risk & Policy

WHAT IT DOES

What memory.store does on Sylex Memory

AI agents use memory.store to create or update resources in Sylex Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sylex Memory environment.

WHY IT NEEDS A POLICY

Why memory.store needs a policy

This tool writes/creates data by storing a memory entry in a persistent vault. It is a Write operation as it adds new data reversibly (memories can presumably be deleted later). The encryption aspect doesn't change the category. Severity is medium because an AI agent could store sensitive, misleading, or unwanted information in persistent memory that affects future agent behavior.

From the tool's definition 'Store a memory' — creates/writes new data; 'Content should be encrypted client-side before' indicates data persistence with encryption

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory.store Rate-limited

memory.store 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.store": {
      "limits": [
        {
          "counter": "memory.store_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 Sylex Memory, so you can run agents against it safely.

FAQ

Questions about memory.store

What does the memory.store tool do? +

Store a memory. Content should be encrypted client-side before. It is categorised as a Write tool in the Sylex Memory 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.store? +

Register the Sylex Memory MCP server in PolicyLayer and add a rule for memory.store: 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 Sylex Memory. Nothing to install.

What risk level is memory.store? +

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

Can I rate-limit memory.store? +

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

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

memory.store is provided by the Sylex Memory MCP server (mastadoonprime/sylex-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.