refresh_api_key

Перевыпускает существующий API-токен. Возвращает новое значение токена (один раз)

SERVERTimeweb SOURCEtimeweb-mcp

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/timeweb-mcp/refresh-api-key.md

WHAT IT DOES

What refresh_api_key does on Timeweb

AI agents call refresh_api_key to retrieve information from Timeweb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`expire`	string	—	Новое время истечения токена в ISO8601 (например 2026-12-31T23:59:59Z). Если не указано — без срока
`token_id`	string	Yes	ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID API-токена, который нужно перевыпустить

Parameters from the server's own tool schema.

RISK

Why refresh_api_key is rated Low

Even though refresh_api_key only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs refresh_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 refresh_api_key, this is the rule to start with:

refresh_api_key Allowed

refresh_api_key is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh_api_key": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every refresh_api_key call is checked against it from then on.

FAQ

Questions about refresh_api_key

What does the refresh_api_key tool do? +

Перевыпускает существующий API-токен. Возвращает новое значение токена (один раз). It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.

What parameters does refresh_api_key accept? +

refresh_api_key accepts 2 parameters: expire, token_id. Required: token_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on refresh_api_key? +

Register the Timeweb MCP server in PolicyLayer and add a rule for refresh_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.

What risk level is refresh_api_key? +

refresh_api_key is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit refresh_api_key? +

Yes. Add a rate_limit block to the refresh_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.

How do I block refresh_api_key completely? +

Set action: deny in the PolicyLayer policy for refresh_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.

What MCP server provides refresh_api_key? +

refresh_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.

KEEP EXPLORING

More on Timeweb, and thousands of servers like it.

This server

All 245 Timeweb tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →