Low Risk

context_session_list

List recent sessions

How to control context_session_list ↓

What context_session_list does on MCP Memory Keeper

AI agents call context_session_list to retrieve information from MCP Memory Keeper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why context_session_list needs a policy

This tool queries and returns a list of existing sessions without creating, modifying, deleting, or executing anything. It is a straightforward read operation on stored context data. The blast radius of misuse is minimal—an agent could only enumerate sessions to understand what work history exists, but cannot alter or delete context data. Severity is low because reading session metadata poses minimal risk.

From the tool's definition Tool name 'context_session_list' and description 'List recent sessions' indicate a retrieval/query operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access context_session_list gives an agent:

How to control context_session_list

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Memory Keeper, and nothing reaches the server without passing your rules. This is the rule we recommend for context_session_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "context_session_list": {}
  }
}

context_session_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Memory Keeper — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about context_session_list

What does the context_session_list tool do? +

List recent sessions. It is categorised as a Read tool in the MCP Memory Keeper MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on context_session_list? +

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

What risk level is context_session_list? +

context_session_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit context_session_list? +

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

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

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

Enforce policy on every MCP Memory Keeper tool call.

Start from MCP Memory Keeper, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

40 MCP Memory Keeper tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.