list_recent_sessions
AI agents call list_recent_sessions to retrieve information from Metis Public Health without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool lists or retrieves historical session data, which is a read-only query operation with no destructive, financial, or execution components. The absence of a description lowers confidence slightly, but the name strongly indicates simple enumeration of existing data. The severity is low because exposing recent session metadata poses minimal risk compared to other tool categories.
From the tool's definition Tool name 'list_recent_sessions' clearly indicates a retrieval operation that lists prior session records without modification or side effects.
Attacks that exploit this kind of access
list_recent_sessions. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for list_recent_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 Metis Public Health. Nothing to install.
list_recent_sessions 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 list_recent_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.
Set action: deny in the PolicyLayer policy for list_recent_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.
list_recent_sessions is provided by the Metis Public Health MCP server (sveritg/metis_ph). 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 →