add_session_step · MCP Memory Server MCP: Risk & Policy

WHAT IT DOES

What add_session_step does on MCP Memory Server

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

WHY IT NEEDS A POLICY

Why add_session_step needs a policy

This tool writes session metadata (recording a step completion) but does not execute arbitrary code, delete data irreversibly, move money, or modify protected files. It creates or updates reversible session tracking records, making it a Write category tool with low severity since session metadata changes have minimal blast radius and can be undone or corrected.

From the tool's definition Tool description states 'Record completion of a step in the current session' – this indicates creating or modifying session tracking data. The name 'add_session_step' and verb 'Record' confirm a write operation that appends or updates session state reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_session_step Rate-limited

add_session_step 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": {
    "add_session_step": {
      "limits": [
        {
          "counter": "add_session_step_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 MCP Memory Server, so you can run agents against it safely.

FAQ

Questions about add_session_step

What does the add_session_step tool do? +

Record completion of a step in the current session. It is categorised as a Write tool in the MCP Memory 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 add_session_step? +

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

What risk level is add_session_step? +

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

Can I rate-limit add_session_step? +

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

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

add_session_step is provided by the MCP Memory Server MCP server (keleshteri/mcp-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.