list_sessions
AI agents call list_sessions to retrieve information from Z3/SMT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about sessions in the Z3/SMT solver server. It performs no modifications, side effects, or code execution—it merely enumerates or returns data. Even if misused by an AI agent, it can only expose metadata about sessions, not cause harm. Severity is low because the blast radius is limited to information disclosure of non-sensitive constraint-solving session states.
From the tool's definition Tool name 'list_sessions' indicates a query/retrieval operation that lists existing sessions without modifying state. No description provided, but the naming pattern and context (sibling tools manage sessions) confirms read-only semantics.
Attacks that exploit this kind of access
list_sessions. It is categorised as a Read tool in the Z3/SMT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Z3/SMT MCP Server MCP server in PolicyLayer and add a rule for list_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 Z3/SMT MCP Server. Nothing to install.
list_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_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_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_sessions is provided by the Z3/SMT MCP Server MCP server (newjerseystyle/z3smt-mcp). 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 →