AI agents call ai_get_session_history to retrieve information from Kali Security MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical session data and conversation logs. It performs a read-only operation that queries existing session information without creating, modifying, deleting, or executing anything. The worst-case misuse would be unauthorized access to conversation history, which is a lower-severity information disclosure risk compared to tools that can modify data or execute code.
From the tool's definition Tool name contains 'get' and description translates to 'Get AI session history - view complete conversation history and analysis progress'. The verb 'get' and 'view' indicate retrieval-only operations with no modification or side effects.
Documented attack patterns abuse exactly the kind of access ai_get_session_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for ai_get_session_history:
{
"version": "1",
"default": "deny",
"tools": {
"ai_get_session_history": {}
}
}ai_get_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.
获取AI会话历史 - 查看完整的对话历史和分析进展. It is categorised as a Read tool in the Kali Security MCP MCP Server, which means it retrieves data without modifying state.
Register the Kali Security MCP server in PolicyLayer and add a rule for ai_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 Kali Security MCP. Nothing to install.
ai_get_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 ai_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.
Set action: deny in the PolicyLayer policy for ai_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.
ai_get_session_history is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.