К содержанию
TelegaFirst

Для AI-агентов: markdown этой страницы — /docs/mcp-tool-secret-put.mdиндекс документации — /llms.txt

secret_put

Обновлено

Store a NEW secret for the business's hosted site (an API token its pages or form handlers call out with). REQUIRES THE OWNER'S CONFIRMATION: call it once without `action_id` and you get back `pending_approval` with an `action_id` — the owner is asked in Telegram to confirm storing a secret under this name. Once they confirm, call again with the SAME `action_id` and the same value, and it is stored. Nothing is kept between the two calls. The value is encrypted at rest and is NEVER returned by any tool — not by this one, not by `secret_list`. A name that already holds a live secret is a conflict: use `secret_rotate` to change a value, or `secret_delete` first to re-use the name.

Права и условия

required_scopes: ALL.

ПолеЗначение
description"Store a NEW secret for the business's hosted site (an API token its pages or form handlers call out with). REQUIRES THE OWNER'S CONFIRMATION: call it once without `action_id` and you get back `pending_approval` with an `action_id` — the owner is asked in Telegram to confirm storing a secret under this name. Once they confirm, call again with the SAME `action_id` and the same value, and it is stored. Nothing is kept between the two calls. The value is encrypted at rest and is NEVER returned by any tool — not by this one, not by `secret_list`. A name that already holds a live secret is a conflict: use `secret_rotate` to change a value, or `secret_delete` first to re-use the name."
domain"site"
name"secret_put"
platform_version"1.0.20"
required_scopes["site:write"]
risk"write"
scope"site:write"
title"Secret Put"

Входные параметры

secret_put: inputSchema

Результат

null