store_conversation · Session Buddy MCP: Risk & Policy

WHAT IT DOES

What store_conversation does on Session Buddy

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

This tool writes conversation data (with vector embeddings) into the session memory store. It creates new records but does not delete or overwrite existing data irreversibly, nor does it execute code or move money. The blast radius is medium because an AI agent could store misleading or polluted conversation memories that affect future semantic search results, corrupting the session's learning history.

From the tool's definition 'Manually store a conversation with embedding support' — creates/writes new conversation data with embeddings into local storage

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

store_conversation Rate-limited

store_conversation 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_conversation": {
      "limits": [
        {
          "counter": "store_conversation_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 store_conversation

What does the store_conversation tool do? +

Manually store a conversation with embedding support. 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 store_conversation? +

Register the Session Buddy MCP server in PolicyLayer and add a rule for store_conversation: 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 store_conversation? +

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

Can I rate-limit store_conversation? +

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

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

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