create_api_key
Mint a project API key. Returns the plaintext exactly once — store it now, it cannot be retrieved later. Editor + owner; subject to the project key policy (see get_key_policy).
This record as markdown: /tools/dev-echorelay-management/create-api-key.md
What create_api_key does on EchoRelay
AI agents use create_api_key to create or update resources in EchoRelay, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EchoRelay environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | Yes | live → paid pool, test → testing pool (rate-limited to the plan's live rate). |
name | string | Yes | Human-readable label, up to 120 characters. |
ttlDays | integer | null | — | Lifetime in days. Omit to use the project's defaultKeyTtlDays from get_key_policy. Null = never expires (owner-only unless editorsMayCreateNonExpiringKeys is se |
Parameters from the server's own tool schema.
Why create_api_key is rated Medium
This tool creates and returns sensitive authentication credentials. While creation is reversible (keys can be revoked), the one-time plaintext return and persistent access grant until revocation makes this a Write operation with high severity. An AI agent misusing this could mint unlimited API keys for unauthorized access to the project.
From the tool's definition Tool description states 'Mint a project API key' and 'Returns the plaintext exactly once — store it now, it cannot be retrieved later.' This creates a new credential artifact with persistent access implications.
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 EchoRelay, 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 EchoRelay, apply this rule, and every create_api_key call is checked against it from then on.
Questions about create_api_key
Mint a project API key. Returns the plaintext exactly once — store it now, it cannot be retrieved later. Editor + owner; subject to the project key policy (see get_key_policy). It is categorised as a Write tool in the EchoRelay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_api_key accepts 3 parameters: mode, name, ttlDays. Required: mode, name. The full parameter table on this page comes from the server's own tool schema.
Register the EchoRelay 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 EchoRelay. 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 EchoRelay MCP server (https://mcp.echorelay.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EchoRelay, and thousands of servers like it.
This server
Across the catalogue