weaviate-store-memory · Weaviate MCP Server MCP

WHAT IT DOES

What weaviate-store-memory does on Weaviate MCP Server

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

WHY IT NEEDS A POLICY

Why weaviate-store-memory needs a policy

This tool writes data to a Weaviate vector database by storing memories for later retrieval. It creates new entries reversibly (no indication of deletion or overwriting), placing it in the Write category. Misuse could result in storing incorrect, sensitive, or malicious data in the knowledge base, giving it a medium severity.

From the tool's definition 'store-memory' and 'Keep the memory for later use, when you are asked to remember something' — creates/stores new data in the Weaviate vector database

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

weaviate-store-memory Rate-limited

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

FAQ

Questions about weaviate-store-memory

What does the weaviate-store-memory tool do? +

Keep the memory for later use, when you are asked to remember something. It is categorised as a Write tool in the Weaviate 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 weaviate-store-memory? +

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

What risk level is weaviate-store-memory? +

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

Can I rate-limit weaviate-store-memory? +

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

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

weaviate-store-memory is provided by the Weaviate MCP Server MCP server (sndani/mcp-localhost-server-weaviate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.