list_agent_sessions

List conversation sessions for an agent. Shows session name (first message), message count, and timestamps.

Server Lens lens-mcp-server
Category Read
Risk class Low
Parameters 11 required

What list_agent_sessions does on Lens

AI agents call list_agent_sessions 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.

ParameterTypeRequiredDescription
agent_id string Yes Agent UUID

Parameters from the server's own tool schema.

Why list_agent_sessions needs a policy

This tool retrieves and queries existing session metadata without creating, modifying, deleting, or executing any operations. It is a straightforward read operation on agent conversation history data with no blast radius if misused by an AI agent—at worst, an agent gains visibility into historical sessions but cannot alter them.

From the tool's definition Tool description states 'List conversation sessions for an agent' with read-only operations (shows/displays session metadata: name, message count, timestamps).

Questions about list_agent_sessions

What does the list_agent_sessions tool do? +

List conversation sessions for an agent. Shows session name (first message), message count, and timestamps. It is categorised as a Read tool in the Lens MCP Server, which means it retrieves data without modifying state.

What parameters does list_agent_sessions accept? +

list_agent_sessions accepts 1 parameter: agent_id. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_agent_sessions? +

Register the Lens MCP server in PolicyLayer and add a rule for list_agent_sessions: 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.

What risk level is list_agent_sessions? +

list_agent_sessions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_agent_sessions? +

Yes. Add a rate_limit block to the list_agent_sessions 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 list_agent_sessions completely? +

Set action: deny in the PolicyLayer policy for list_agent_sessions. 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 list_agent_sessions? +

list_agent_sessions 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.