preserve_current_context · Session Buddy MCP: Risk & Policy

WHAT IT DOES

What preserve_current_context does on Session Buddy

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

This tool writes/stores the current development context to persistent memory. It creates or updates stored state, which is a reversible write operation. No code execution, deletion, or financial implications are evident. Confidence is moderate because the description is vague about what exactly is preserved and where.

From the tool's definition 'Preserve current development context before an interruption' — saves/stores context data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

preserve_current_context Rate-limited

preserve_current_context 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": {
    "preserve_current_context": {
      "limits": [
        {
          "counter": "preserve_current_context_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 preserve_current_context

What does the preserve_current_context tool do? +

Preserve current development context before an interruption. 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 preserve_current_context? +

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

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

Can I rate-limit preserve_current_context? +

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

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

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