get_session_history

Get history of commits in current session

SERVERCode MCP Server SOURCEagentics-ai/code-mcp

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/agentics-ai-code-mcp/get-session-history.md

WHAT IT DOES

What get_session_history does on Code MCP Server

AI agents call get_session_history to retrieve information from Code MCP Server 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 queries and retrieves Git commit history from the current session. It performs a read-only operation that does not create, modify, delete, or execute any operations. The data retrieved is historical metadata about commits, which carries minimal risk if accessed by an AI agent, as viewing commit history cannot cause damage to the codebase or system.

From the tool's definition Tool name 'get_session_history' and description 'Get history of commits in current session' indicates retrieval of historical data without modification or side effects.

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 Code MCP Server, 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 Code MCP Server, 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 history of commits in current session. It is categorised as a Read tool in the Code MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_session_history? +

Register the Code MCP Server 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 Code MCP Server. 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 Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Code MCP Server, and thousands of servers like it.

This server

All 73 Code MCP Server 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 →