session_history

List the undo history (index + description for each snapshot).

SERVERMcp Anything SOURCEZaymadkid/mcp-anything

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/mcp-anything/session-history.md

WHAT IT DOES

What session_history does on Mcp Anything

AI agents call session_history to retrieve information from Mcp Anything 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_history is rated Low

This tool retrieves and queries historical snapshots from an undo system. It returns data (indices and descriptions) without modifying, executing, or deleting anything. This is a pure read operation with minimal security impact, as it only exposes metadata about previous states rather than performing any state change.

From the tool's definition Tool name is 'session_history' and description states 'List the undo history (index + description for each snapshot)'. The verb 'List' indicates a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs session_history safely

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

session_history Allowed

session_history 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_history": {}
  }
}

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

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

FAQ

Questions about session_history

What does the session_history tool do? +

List the undo history (index + description for each snapshot). It is categorised as a Read tool in the Mcp Anything MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on session_history? +

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

What risk level is session_history? +

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

Can I rate-limit session_history? +

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

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

session_history is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Anything, and thousands of servers like it.

This server

All 261 Mcp Anything tools →

Across the catalogue

The MCP Attack Database →

Guides

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