get_session_history

A read tool on the CogniRepo MCP server.

SERVERCogniRepo SOURCEpypi:cognirepo

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/ashlesh-t-cognirepo/get-session-history.md

WHAT IT DOES

What get_session_history does on CogniRepo

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

RISK

Why get_session_history is rated Low

This tool retrieves historical session information without side effects. It follows the Read pattern of querying/fetching data. While the description is empty, the naming convention and server context strongly indicate a data retrieval function. Low severity due to read-only nature and typical low sensitivity of session metadata, though confidence is slightly reduced due to missing explicit description.

From the tool's definition Tool name 'get_session_history' indicates retrieval of stored session data. The server description emphasizes 'persistent memory' and 'session history' for avoiding context loss.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_session_history safely

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

get_session_history Allowed

get_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": {
    "get_session_history": {}
  }
}

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

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

FAQ

Questions about get_session_history

What does the get_session_history tool do? +

get_session_history is a read tool on the CogniRepo MCP server. It is categorised as a Read tool in the CogniRepo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_session_history? +

Register the CogniRepo MCP server in PolicyLayer and add a rule for get_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 CogniRepo. Nothing to install.

What risk level is get_session_history? +

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

Can I rate-limit get_session_history? +

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

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

get_session_history is provided by the CogniRepo MCP server (pypi:cognirepo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CogniRepo, and thousands of servers like it.

This server

All 34 CogniRepo tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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