# get_creator_audience

Get creator audience demographics. 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_audience`. HTML page: https://policylayer.com/tools/com-getcims-mcp/get-creator-audience

## Facts

- Tool: `get_creator_audience`
- 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: Read (Low risk)
- Registry record: grade A, identity unverified
- Server auth posture: gated
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## 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_audience",
    "arguments": {}
  }
}
```

## Why get_creator_audience is rated Low

The primary function is retrieving audience demographic data (Read category). However, the financial friction—requiring payment to call the tool—elevates severity to medium. While the tool itself doesn't move money (which would be Financial category), it gatekeeps access behind a payment wall, creating moderate risk if an agent unexpectedly triggers billable API calls.

From the tool's own definition: "Tool description states 'Get creator audience demographics' which is a data retrieval operation. However, the mention of 'x402 payment requirements' indicates financial implications when the tool is actually invoked."

## Use case

AI agents call get_creator_audience to retrieve information from Mcp 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 Mcp:

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

## Other tools on Mcp (6)

- `get_creator_statistics` — Financial — https://policylayer.com/tools/com-getcims-mcp/get-creator-statistics.md
- `get_creator` — Read — https://policylayer.com/tools/com-getcims-mcp/get-creator.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