AI agents call list-sessions to retrieve information from CodeAnalysis 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 or queries session data with no side effects. It follows the pattern of Read category tools (list, get, fetch operations). The empty description lowers confidence slightly, but the naming convention and context strongly suggest a non-destructive retrieval operation. Severity is low because unauthorized access to session metadata poses minimal risk compared to other tool categories.
From the tool's definition Tool name 'list-sessions' indicates data retrieval. The tool lists existing sessions without modifying or deleting them. Context of sibling tools (create-session, clear-session) shows this server manages sessions; list-sessions is the query variant.
Documented attack patterns abuse exactly the kind of access list-sessions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeAnalysis MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-sessions:
{
"version": "1",
"default": "deny",
"tools": {
"list-sessions": {}
}
}list-sessions 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-sessions. It is categorised as a Read tool in the CodeAnalysis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CodeAnalysis 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 CodeAnalysis 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 CodeAnalysis MCP Server MCP server (0xjcf/mcp_codeanalysis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeAnalysis MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
31 CodeAnalysis MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.