create_api_key · Cryptosense MCP: Risk & Policy

WHAT IT DOES

What create_api_key does on Cryptosense

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.

WHY IT NEEDS A POLICY

Why create_api_key needs a policy

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 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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_api_key Rate-limited

create_api_key stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cryptosense, so you can run agents against it safely.

FAQ

Questions about create_api_key

What does the create_api_key tool do? +

Generate a new CryptoSense API key for the given email address. It is categorised as a Write tool in the Cryptosense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_api_key? +

Register the Cryptosense MCP server in PolicyLayer and add a rule for create_api_key: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Cryptosense. Nothing to install.

What risk level is create_api_key? +

create_api_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_api_key? +

Yes. Add a rate_limit block to the create_api_key rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block create_api_key completely? +

Set action: deny in the PolicyLayer policy for create_api_key. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides create_api_key? +

create_api_key is provided by the Cryptosense MCP server (josephibra/cryptosense-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.