# get_creator_statistics

Get time-series creator statistics. When shown as a paid stub, calling this tool returns x402 payment requirements for the REST endpoint.

Agent View of the PolicyLayer registry record for `get_creator_statistics`. HTML page: https://policylayer.com/tools/com-getcims-mcp/get-creator-statistics

## Facts

- Tool: `get_creator_statistics`
- Server: Mcp (`https://api.getcims.com/functions/v1/mcp`) — https://policylayer.com/tools/com-getcims-mcp.md
- Homepage: https://github.com/https://api.getcims.com/functions/v1/mcp
- Risk category: Financial (Critical risk)
- Registry record: grade A, identity unverified
- Server auth posture: gated
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Approval-gated

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `creatorId` | number | no |  |

Parameters from the server's own tool schema.

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

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

## Why get_creator_statistics is rated Critical

Although the tool's primary function is Read (retrieving time-series creator statistics), the explicit mention of x402 payment requirements means calling it can commit financial obligations. Per the rules, Financial is the most severe applicable category and takes precedence over Read.

From the tool's own definition: "'When shown as a paid stub, calling this tool returns x402 payment requirements for the REST endpoint' — invoking this tool may trigger a financial payment obligation (HTTP 402 Payment Required)"

## Use case

AI agents use get_creator_statistics to commit financial operations through Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.

## Recommended policy (PolicyLayer)

Verdict: **Approval-gated**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_creator_statistics": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

## Other tools on Mcp (6)

- `get_creator` — Read — https://policylayer.com/tools/com-getcims-mcp/get-creator.md
- `get_creator_audience` — Read — https://policylayer.com/tools/com-getcims-mcp/get-creator-audience.md
- `get_creator_cpm` — Read — https://policylayer.com/tools/com-getcims-mcp/get-creator-cpm.md
- `get_creator_posts` — Read — https://policylayer.com/tools/com-getcims-mcp/get-creator-posts.md
- `get_creator_statistic` — Read — https://policylayer.com/tools/com-getcims-mcp/get-creator-statistic.md
- `get_creators` — Read — https://policylayer.com/tools/com-getcims-mcp/get-creators.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=com-getcims-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-getcims-mcp