list_conversations
List all conversation IDs currently stored in this MCP process memory. This tool takes no parameters and does not call the DeepSeek API. Useful for debugging conversation persistence behavior.
This record as markdown: /tools/deepseek-mcp-server/list-conversations.md
What list_conversations does on DeepSeek MCP Server
AI agents call list_conversations to retrieve information from DeepSeek MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_conversations is rated Low
This tool retrieves and displays existing conversation IDs from local memory without modifying, deleting, or executing any operations. It has a minimal blast radius—an AI agent could at worst discover conversation IDs but cannot act upon them without other tools. The lack of parameters and API calls further confirms it is a read-only data retrieval function.
From the tool's definition Tool description states it 'List all conversation IDs currently stored in this MCP process memory' and 'does not call the DeepSeek API'. The verb 'list' combined with 'takes no parameters' indicates a simple retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_conversations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DeepSeek MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_conversations, this is the rule to start with:
list_conversations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect DeepSeek MCP Server, apply this rule, and every list_conversations call is checked against it from then on.
Questions about list_conversations
List all conversation IDs currently stored in this MCP process memory. This tool takes no parameters and does not call the DeepSeek API. Useful for debugging conversation persistence behavior. It is categorised as a Read tool in the DeepSeek MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DeepSeek MCP Server MCP server in PolicyLayer and add a rule for list_conversations: 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 DeepSeek MCP Server. Nothing to install.
list_conversations 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_conversations 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_conversations. 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_conversations is provided by the DeepSeek MCP Server MCP server (deepseek-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DeepSeek MCP Server, and thousands of servers like it.
This server
Across the catalogue