session_info

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/session-info.md

WHAT IT DOES

What session_info does on Claude Flow

AI agents call session_info to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why session_info is rated Low

This tool queries and returns session metadata and state (agent definitions, swarm topology, memory, history) without modifying or deleting data. It is clearly a Read operation.

From the tool's definition 'Get detailed session information' and 'restoring agent definitions, swarm topology, memory store, breaker history' — retrieves and queries state without modifying it.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs session_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For session_info, this is the rule to start with:

session_info Allowed

session_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "session_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every session_info call is checked against it from then on.

FAQ

Questions about session_info

What does the session_info tool do? +

Get detailed session information Use when native conversation memory is wrong because you need durable cross-session state — restoring agent definitions, swarm topology, memory store, breaker history. For in-session continuation only, no tool needed. Pair with session_save before exiting and session_restore on resume. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on session_info? +

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

What risk level is session_info? +

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

Can I rate-limit session_info? +

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

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

session_info is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

get_team_info on CTFtime MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →