get_session_conversation
AI agents call get_session_conversation to retrieve information from Mcp Copilotcli History without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves conversation data from local Copilot history without modifying or executing anything. It performs a straightforward query/fetch operation consistent with the server's stated purpose of 'searching and analyzing' stored conversations. No write, delete, code execution, or financial operations are implied.
From the tool's definition Tool name 'get_session_conversation' and server purpose describe retrieval of GitHub Copilot conversation history. Sibling tools include 'list_recent_sessions', 'search_sessions', 'get_session_stats'—all read operations.
Attacks that exploit this kind of access
get_session_conversation. It is categorised as a Read tool in the Mcp Copilotcli History MCP Server, which means it retrieves data without modifying state.
Register the Mcp Copilotcli History MCP server in PolicyLayer and add a rule for get_session_conversation: 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 Copilotcli History. Nothing to install.
get_session_conversation 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 get_session_conversation 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 get_session_conversation. 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.
get_session_conversation is provided by the Mcp Copilotcli History MCP server (micromichaelie/mcp-copilotcli-history). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →