extract_and_store_memory_tool · Session Buddy MCP

WHAT IT DOES

What extract_and_store_memory_tool does on Session Buddy

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

WHY IT NEEDS A POLICY

Why extract_and_store_memory_tool needs a policy

The tool performs two operations: extraction (read-like) and persistence to v2 tables (write). The dominant effect is writing/storing data, making Write the appropriate category. Severity is medium because it modifies persistent storage (memory/entity tables), but the blast radius is limited to the session memory system rather than critical infrastructure.

From the tool's definition 'Extract entities using cascade and persist to v2 tables' — the tool extracts data and writes/persists it to storage tables

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

extract_and_store_memory_tool Rate-limited

extract_and_store_memory_tool 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": {
    "extract_and_store_memory_tool": {
      "limits": [
        {
          "counter": "extract_and_store_memory_tool_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 Session Buddy, so you can run agents against it safely.

FAQ

Questions about extract_and_store_memory_tool

What does the extract_and_store_memory_tool tool do? +

Extract entities using cascade and persist to v2 tables (when enabled). It is categorised as a Write tool in the Session Buddy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on extract_and_store_memory_tool? +

Register the Session Buddy MCP server in PolicyLayer and add a rule for extract_and_store_memory_tool: 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 Session Buddy. Nothing to install.

What risk level is extract_and_store_memory_tool? +

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

Can I rate-limit extract_and_store_memory_tool? +

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

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

extract_and_store_memory_tool is provided by the Session Buddy MCP server (lesleslie/session-buddy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.