edit_api_key
Изменяет имя и/или флаг is_able_to_delete API-токена по его ID
This record as markdown: /tools/timeweb-mcp/edit-api-key.md
What edit_api_key does on Timeweb
AI agents use edit_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 | — | Новое имя токена (опц.) |
token_id | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID API-токена (UUID) |
is_able_to_delete | boolean | — | Разрешить/запретить удалять сервисы этим токеном без подтверждения (опц.) |
Parameters from the server's own tool schema.
Why edit_api_key is rated Medium
This tool reversibly modifies API token metadata and security settings. It is a Write operation rather than Destructive because the changes are reversible and it does not delete the token itself. However, the is_able_to_delete flag modification elevates severity to high, as it could grant or revoke the ability to perform irreversible operations through that token.
From the tool's definition Tool description (translated): 'Changes the name and/or is_able_to_delete flag of an API token by its ID'. This modifies properties of an API key, including a critical security flag (is_able_to_delete) that controls destructive permissions.
Attacks that exploit this kind of access
The rule that runs edit_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 edit_api_key, this is the rule to start with:
edit_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 edit_api_key call is checked against it from then on.
Questions about edit_api_key
Изменяет имя и/или флаг is_able_to_delete API-токена по его ID. 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.
edit_api_key accepts 3 parameters: name, token_id, is_able_to_delete. Required: token_id. 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 edit_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.
edit_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 edit_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 edit_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.
edit_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