// SCAN REPORT

Claude Usage MCP Server

3 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

1 can modify or destroy data

2 read-only

3 tools total

Community server · catalogue entry verified 03/07/2026

How to control Claude Usage MCP Server ↓

TOOL MAP

What Claude Usage MCP Server exposes to your agents

Read (2) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Claude Usage MCP Server tools

Execute · Medium claude_login This tool triggers an external browser operation (opening a browser window) to perform authentication.

1 of Claude Usage MCP Server's 3 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Claude Usage MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Usage MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "check_claude_auth": {
    "limits": [
      {
        "counter": "check_claude_auth_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Claude Usage MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CLAUDE USAGE →

Instant setup, no code required.

FULL CATALOGUE

All 3 Claude Usage MCP Server tools

EXECUTE 1 tools

Execute claude_login Open a browser window to authenticate with Claude. Use this if get_claude_usage fails due to authentication.

READ 2 tools

Read check_claude_auth Check if the current session is authenticated with Claude. Read get_claude_usage Fetch Claude usage data from the dashboard. Returns daily token usage information.

FAQ

Questions about Claude Usage MCP Server

Is the Claude Usage MCP Server MCP server safe to use without restrictions? +

The Claude Usage MCP Server server is primarily read-only with 2 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Claude Usage MCP Server MCP server expose? +

3 tools across 2 categories: Read, Write. 2 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Claude Usage MCP Server? +

Register the Claude Usage MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Claude Usage MCP Server tool call.

Deterministic rules across all 3 Claude Usage MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CLAUDE USAGE →

Instant setup, no code required.

3 Claude Usage MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.