# get_user_balance

Return the current DeepSeek account balance and availability status. This tool takes no parameters and is read-only. Use it for account health checks when diagnosing provider-side failures.

Agent View of the PolicyLayer registry record for `get_user_balance`. HTML page: https://policylayer.com/tools/deepseek-mcp-server/get-user-balance

## Facts

- Tool: `get_user_balance`
- 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": "get_user_balance",
    "arguments": {}
  }
}
```

## Why get_user_balance is rated Low

This tool only retrieves account balance and status data with no side effects or parameters. It is a pure read operation used for diagnostics and account health checks. While balance information could be considered sensitive, the tool itself performs no risky actions—it simply queries existing data. Severity is low because misuse would only expose information already available to the account holder.

From the tool's own definition: "Tool description explicitly states 'read-only' and 'Return the current DeepSeek account balance'. The function retrieves account balance information without modifying, deleting, or executing operations."

## Use case

AI agents call get_user_balance 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": {
    "get_user_balance": {}
  }
}
```

## 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
- `list_conversations` — Read — https://policylayer.com/tools/deepseek-mcp-server/list-conversations.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