This record as markdown: /tools/timeweb-mcp/delete-api-key.md
What delete_api_key does on Timeweb
AI agents call delete_api_key to permanently remove resources in Timeweb, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
token_id | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID API-токена |
Parameters from the server's own tool schema.
Why delete_api_key is rated Critical
This tool permanently removes an API key/token, which cannot be undone. Deletion of authentication credentials is irreversible and represents the most severe category. An AI agent misusing this could lock legitimate users out of API access or compromise security by orphaning credentials. This is Destructive rather than Write because the action cannot be reversed.
From the tool's definition Tool name is 'delete_api_key' and description states 'Удаляет API-токен по его ID' (Russian: 'Deletes API-token by its ID'). The verb 'delete' and 'Удаляет' both indicate irreversible removal of a resource.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_api_key, this is the rule to start with:
delete_api_key is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every delete_api_key call is checked against it from then on.
Questions about delete_api_key
Удаляет API-токен по его ID. It is categorised as a Destructive tool in the Timeweb MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_api_key accepts 1 parameter: token_id. 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 delete_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.
delete_api_key is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue