create_api_key
Создает новый API-токен. Значение токена возвращается один раз и должно быть сохранено
This record as markdown: /tools/timeweb-mcp/create-api-key.md
What create_api_key does on Timeweb
AI agents use create_api_key to create or update resources in Timeweb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Timeweb environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - имя для создаваемого API-токена |
expire | string | — | Дата и время истечения токена в ISO8601 (например 2026-12-31T23:59:59Z). Если не указано — токен без срока |
projects | array | — | Список ID проектов, к которым ограничивается токен. Пусто/не указано — доступ ко всем проектам |
is_able_to_delete | boolean | — | Разрешить удаление сервисов этим токеном без подтверждения через Telegram (по умолчанию — политика аккаунта) |
Parameters from the server's own tool schema.
Why create_api_key is rated Medium
An AI agent can call create_api_key faster than any human can review: one bad instruction and it creates or modifies resources in Timeweb by the hundred, each call as confident as the last.
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 Timeweb, 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 Timeweb, apply this rule, and every create_api_key call is checked against it from then on.
Questions about create_api_key
Создает новый API-токен. Значение токена возвращается один раз и должно быть сохранено. It is categorised as a Write tool in the Timeweb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_api_key accepts 4 parameters: name, expire, projects, is_able_to_delete. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Timeweb 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 Timeweb. 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 Timeweb MCP server (timeweb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Timeweb, and thousands of servers like it.
This server
Across the catalogue