# create_api_key

Generate a new CryptoSense API key for the given email address.

Agent View of the PolicyLayer registry record for `create_api_key`. HTML page: https://policylayer.com/tools/josephibra-cryptosense-mcp/create-api-key

## Facts

- Tool: `create_api_key`
- Server: Cryptosense (`josephibra/cryptosense-mcp`) — https://policylayer.com/tools/josephibra-cryptosense-mcp.md
- Homepage: https://github.com/josephibra/cryptosense-mcp
- Risk category: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why create_api_key is rated Medium

This tool creates new API credentials, which is a reversible data modification (Write category). However, severity is high because an AI agent generating API keys for arbitrary email addresses could enable unauthorized account access, credential proliferation, or account takeover attacks.

From the tool's own definition: "Tool name 'create_api_key' and description 'Generate a new CryptoSense API key' indicate irreversible creation of authentication credentials for a specific email address."

## Use case

AI agents use create_api_key to create or update resources in Cryptosense, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cryptosense environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Cryptosense:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_api_key": {
      "limits": [
        {
          "counter": "create_api_key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Cryptosense (35)

- `run_query` — Execute — https://policylayer.com/tools/josephibra-cryptosense-mcp/run-query.md
- `async_tool` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/async-tool.md
- `custom_name` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/custom-name.md
- `greeting` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/greeting.md
- `log_progress` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/log-progress.md
- `multiply` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/multiply.md
- `my_task` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/my-task.md
- `my_tool` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/my-tool.md
- `tool_with_context` — Other — https://policylayer.com/tools/josephibra-cryptosense-mcp/tool-with-context.md
- `check_worker_status` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/check-worker-status.md
- `compare` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/compare.md
- `echo_tool` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/echo-tool.md
- `get_auth_type` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/get-auth-type.md
- `get_client_ip` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/get-client-ip.md
- `get_info` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/get-info.md
- `get_my_emails` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/get-my-emails.md
- `get_user_id` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/get-user-id.md
- `greet` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/greet.md
- `introspect` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/introspect.md
- `list_files` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/list-files.md
- `long_running_task` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/long-running-task.md
- `market_overview` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/market-overview.md
- `portfolio_value` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/portfolio-value.md
- `price` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/price.md
- `read_file` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/read-file.md
- `top_coins` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/top-coins.md
- `trending` — Read — https://policylayer.com/tools/josephibra-cryptosense-mcp/trending.md
- `add` — Write — https://policylayer.com/tools/josephibra-cryptosense-mcp/add.md
- `add_expense` — Write — https://policylayer.com/tools/josephibra-cryptosense-mcp/add-expense.md
- `save` — Write — https://policylayer.com/tools/josephibra-cryptosense-mcp/save.md
- …and 5 more: https://policylayer.com/tools/josephibra-cryptosense-mcp.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=josephibra-cryptosense-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/josephibra-cryptosense-mcp