# 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.

Agent View of the PolicyLayer registry record for `list_conversations`. HTML page: https://policylayer.com/tools/deepseek-mcp-server/list-conversations

## Facts

- Tool: `list_conversations`
- Server: DeepSeek MCP Server (`deepseek-mcp-server`) — https://policylayer.com/tools/deepseek-mcp-server.md
- Install: `npx -y deepseek-mcp-server`
- Homepage: https://github.com/DMontgomery40/deepseek-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_conversations",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches DeepSeek MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_conversations": {}
  }
}
```

## Other tools on DeepSeek MCP Server (6)

- `reset_conversation` — Destructive — https://policylayer.com/tools/deepseek-mcp-server/reset-conversation.md
- `chat_completion` — Execute — https://policylayer.com/tools/deepseek-mcp-server/chat-completion.md
- `completion` — Execute — https://policylayer.com/tools/deepseek-mcp-server/completion.md
- `create_response` — Execute — https://policylayer.com/tools/deepseek-mcp-server/create-response.md
- `get_user_balance` — Read — https://policylayer.com/tools/deepseek-mcp-server/get-user-balance.md
- `list_models` — Read — https://policylayer.com/tools/deepseek-mcp-server/list-models.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=deepseek-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deepseek-mcp-server