List all local chat sessions stored under chats/.
AI agents call list_chat_sessions to retrieve information from Grok 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 queries existing chat session metadata from the `chats/` directory. It performs no creation, modification, deletion, code execution, or financial operations. The operation is read-only and non-destructive, making it a Read category tool with low severity since the information returned consists of session metadata that an AI agent could access without causing harm.
From the tool's definition Tool name 'list_chat_sessions' and description 'List all local chat sessions' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_chat_sessions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Grok MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_chat_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"list_chat_sessions": {}
}
}list_chat_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 all local chat sessions stored under chats/. It is categorised as a Read tool in the Grok MCP MCP Server, which means it retrieves data without modifying state.
Register the Grok MCP server in PolicyLayer and add a rule for list_chat_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 Grok MCP. Nothing to install.
list_chat_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_chat_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_chat_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_chat_sessions is provided by the Grok MCP server (merterbak/grok-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Grok MCP, 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.
22 Grok MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.