List all saved session states for this agent and session. Useful for seeing what context is available after a connection recovery.
AI agents call list_session_states to retrieve information from Agent MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing session state data without creating, modifying, or deleting any information. It is a read-only operation with no side effects, making it a Read category tool. Severity is low because listing session states poses minimal security risk—it reveals only metadata about available contexts, not sensitive operational data itself.
From the tool's definition Tool name 'list_session_states' and description 'List all saved session states' indicate a retrieval operation with no modification capability. The purpose is to query and display available session context data.
Documented attack patterns abuse exactly the kind of access list_session_states gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_session_states:
{
"version": "1",
"default": "deny",
"tools": {
"list_session_states": {}
}
}list_session_states 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.
List all saved session states for this agent and session. Useful for seeing what context is available after a connection recovery. It is categorised as a Read tool in the Agent MCP MCP Server, which means it retrieves data without modifying state.
Register the Agent MCP server in PolicyLayer and add a rule for list_session_states: 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 Agent MCP. Nothing to install.
list_session_states 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_session_states 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_session_states. 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_session_states is provided by the Agent MCP server (rinadelph/agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Agent MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Agent MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.