session_recap

ServerHydraMCP
CategoryRead

WHAT IT DOES

What session_recap does on HydraMCP

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

THE RISK

Low Risk

Why session_recap needs a policy

This tool retrieves and summarizes historical session data without modifying, deleting, or executing external operations. It is a read-only operation that queries stored sessions and synthesizes them into a recap. The explicit mention that 'Claude never sees the raw session data' further confirms the tool operates in a safe, read-only manner. No side effects, no data modification, no command execution.

From the tool's definition Tool description states it 'Read[s] previous Claude Code sessions from disk' and 'generate[s] a smart-sized recap'. The output is a markdown summary, not modification or deletion of data.

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

POLICY

How to control session_recap

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

policy.json

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

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More HydraMCP tools

Execute ask_model Query any AI model with a prompt. Returns the model Execute compare_models Query 2-5 models in parallel with the same prompt. Returns side-by-side comparison with la Execute consensus Query 3-7 models and aggregate responses using voting strategy (majority/supermajority/una Execute synthesize Query 2-5 models in parallel, then combine their best ideas into one answer. Returns a syn Read analyze_file Offload file analysis to a worker model. The file is read server-side — it never enters yo Read list_models List all available models across all providers. Run this first to see what you can query. Read smart_read Surgical code extraction from files. Returns ONLY relevant code sections with line numbers

All 8 HydraMCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about session_recap

What does the session_recap tool do? +

Read previous Claude Code sessions from disk and generate a smart-sized recap using a large-context model. Claude never sees the raw session data — only the distilled summary. OUTPUT: Returns markdown starting with. It is categorised as a Read tool in the HydraMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on session_recap? +

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

What risk level is session_recap? +

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

Can I rate-limit session_recap? +

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

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

session_recap is provided by the Hydra MCP server (pickle-pixel/hydramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every HydraMCP tool call.

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

CHECK YOUR STACK →

Free to start. No card required.

8 HydraMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.