List BotCLI sessions with optional filters
AI agents call session_list to retrieve information from Climux without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward listing/query tool. It retrieves session metadata for informational purposes. The presence of 'optional filters' suggests parameterized querying, but does not change the fundamental read-only nature. No side effects or state changes are implied. Blast radius is minimal—misuse would only expose session information the agent already has access to.
From the tool's definition Tool name 'session_list' and description 'List BotCLI sessions with optional filters' indicate a read-only operation that retrieves and displays session information without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access session_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Climux, and nothing reaches the server without passing your rules. This is the rule we recommend for session_list:
{
"version": "1",
"default": "deny",
"tools": {
"session_list": {}
}
}session_list 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 BotCLI sessions with optional filters. It is categorised as a Read tool in the Climux MCP Server, which means it retrieves data without modifying state.
Register the Climux MCP server in PolicyLayer and add a rule for session_list: 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 Climux. Nothing to install.
session_list 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 session_list 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 session_list. 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.
session_list is provided by the Climux MCP server (veithly/climux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Climux, 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.
9 Climux tools catalogued and risk-classified — across an index of 43,000+ MCP servers.