AI agents call get_session_history to retrieve information from Lens without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | string | Yes | Agent UUID |
session_id | string | Yes | Session UUID (from list_agent_sessions) |
Parameters from the server's own tool schema.
This tool retrieves and queries existing conversation history data from an agent session. It performs no creation, modification, deletion, or execution of code/commands. The action is purely informational and read-only, matching the 'Read' category definition of retrieving or querying data with no side effects.
From the tool's definition Tool name 'get_session_history' and description 'Get the full message history for an agent session. Returns the conversation in chronological order.' indicate a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Get the full message history for an agent session. Returns the conversation in chronological order. It is categorised as a Read tool in the Lens MCP Server, which means it retrieves data without modifying state.
get_session_history accepts 2 parameters: agent_id, session_id. Required: agent_id, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Lens 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 Lens. Nothing to install.
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 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 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.
get_session_history is provided by the Lens MCP server (lens-mcp-server). 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 →