create_api_key
Create a new live API key. Only available for active accounts. The key is shown once — store it immediately.
This record as markdown: /tools/dev-aic0rt3x-memory-mcp/create-api-key.md
What create_api_key does on AI Cortex Storage
AI agents use create_api_key to create or update resources in AI Cortex Storage, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AI Cortex Storage environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
label | string | — | Human-readable label (e.g. 'claude-desktop') |
Parameters from the server's own tool schema.
Why create_api_key is rated Medium
This tool creates a new API key, which is a reversible data creation action (Write category). However, it carries high severity because: (1) API keys grant authentication and access to cloud storage and other sensitive operations; (2) the one-time display nature means loss of the key cannot be recovered except via revocation and re-creation; (3) a malicious agent could create numerous keys to escalate access or…
From the tool's definition Tool description states 'Create a new live API key' — a write operation that generates a new credential object with persistent effects.
Attacks that exploit this kind of access
The rule that runs create_api_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AI Cortex Storage, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_api_key, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect AI Cortex Storage, apply this rule, and every create_api_key call is checked against it from then on.
Questions about create_api_key
Create a new live API key. Only available for active accounts. The key is shown once — store it immediately. It is categorised as a Write tool in the AI Cortex Storage MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_api_key accepts 1 parameter: label. The full parameter table on this page comes from the server's own tool schema.
Register the AI Cortex Storage 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 AI Cortex Storage. Nothing to install.
create_api_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
create_api_key is provided by the AI Cortex Storage MCP server (https://memory.aic0rt3x.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AI Cortex Storage, and thousands of servers like it.
This server
Across the catalogue