Show command/evidence history for the current session
AI agents call session_history to retrieve information from Kali MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents logs or records of prior session activity. It performs a passive query operation that neither modifies state, executes commands, deletes data, nor moves funds. The read-only nature and absence of side effects place it squarely in the Read category with low severity, as misuse would only expose historical information already captured during the session.
From the tool's definition Tool name 'session_history' and description 'Show command/evidence history for the current session' indicate retrieval and display of historical data with no modification, deletion, or execution of new operations.
Documented attack patterns abuse exactly the kind of access session_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for session_history:
{
"version": "1",
"default": "deny",
"tools": {
"session_history": {}
}
}session_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Show command/evidence history for the current session. It is categorised as a Read tool in the Kali MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kali MCP Server 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 Kali MCP Server. Nothing to install.
session_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
session_history is provided by the Kali MCP Server MCP server (k3nn3dy-ai/kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kali MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 Kali MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.