session_manager

THE RISK

Critical Risk

Why session_manager needs a policy

The tool explicitly handles session deletion ('세션 삭제'), which is an irreversible destructive operation. It also manages setting/unsetting active sessions and toggling auto-link features. Per the severity rules, when a tool spans categories, the most severe applies — Destructive (session deletion) outranks Write (configuration changes).

From the tool's definition 세션 삭제 (session deletion), 활성 세션 설정/해제, 자동 링크 활성화/비활성화 — includes irreversible session deletion alongside configuration changes

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

POLICY

How to control session_manager

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "session_manager"
  ]
}

session_manager disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Work Memory MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Work Memory MCP Server tools

Destructive delete_work_memory 종합 데이터 삭제 도구 - 작업기억, 세션, 히스토리, 검색인덱스 등 카테고리별 세분화된 삭제 지원. 단일/복수/조건부/전체 삭제 가능 Execute index_repair 누락된 인덱스를 수동으로 복구하고 인덱싱 프로세스를 검증합니다 Execute optimize_database 데이터베이스를 최적화하고 인덱스 커버리지를 분석합니다. VACUUM, ANALYZE, 인덱스 최적화 포함 Execute optimize_search_index 검색 인덱스를 최적화합니다. 고아 키워드 제거, 유사 키워드 병합, 압축 등을 수행하여 검색 성능을 향상시킵니다. Write batch_operations 여러 메모리 작업을 효율적으로 일괄 처리합니다 Write add_work_memory 작업 내용을 SQLite 데이터베이스에 저장합니다. 할일 저장 시 context(배경정보)와 content(작업내용)가 필요합니다. Write restore_memory_version 이전 버전으로 메모리를 복구합니다. 전체/선택적/미리보기 모드 지원 Write update_work_memory 기존 메모리의 내용을 업데이트합니다. 할일 완료 시 content(작업요약)와 result_content(결과물)를 함께 업데이트하세요.

All 24 Work Memory MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Work Memory MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about session_manager

What does the session_manager tool do? +

세션을 관리합니다. 활성 세션 설정/해제, 세션 삭제, 자동 링크 활성화/비활성화를 처리합니다. It is categorised as a Destructive tool in the Work Memory MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on session_manager? +

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

What risk level is session_manager? +

session_manager is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit session_manager? +

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

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

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

Enforce policy on every Work Memory MCP Server tool call.

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

CHECK YOUR STACK →