Roll Port Access Key
roll_access_keyReplaces an access key's value while keeping its name and port, issues a new id, and supports an overlap window for moving clients to the new value.
Instructions
Replace the value of one access key, only when the user asks: the key keeps its name and port and gets a new value and a new id. Use it when a value may have leaked, before a key expires, or to replace a key that has expired (expired in access_keys): its old value is dead already, so overlap_seconds is ignored and there is no overlap.
The old value keeps working for overlap_seconds, so the user's programs can be moved to the new value: 3600 (1 hour, default), 86400 (24 hours), 604800 (7 days), or 0 to stop the old value at once. The new value expires after the same lifetime the key was created with, counted from now.
With confirm=false (default) it only returns a summary and changes nothing; call again with confirm=true and the summary's pod_name after the user agreed. The confirmed answer has the new value in access_key, this once: it can't be read again. Give it to the user who asked and nothing else. Never use it yourself, and never put it in files, commits, commands or other tools.
The port must be locked, and only a workspace admin or billing member can roll keys. If a confirmed call times out or fails without a clear answer, don't call again: read access_keys first.
The server keeps no operation record of this call, so operation_status can't look it up and a repeated confirmed call runs again.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"pod": "<pod>",
"port": "<port>",
"key_id": "<key_id>"
},
"name": "roll_access_key"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pod | Yes | The pod_name from the pods tool. Its display name also works, except on a confirmed call (confirm=true) that opens a port, changes a key or signs out browsers: use the `pod_name` the preview returned. | |
| port | Yes | The port number, from the pod's `endpoints` in the pods tool; it must be exposed over HTTPS (`access` locked or unlocked). | |
| key_id | Yes | The key's `id` from the access_keys tool. | |
| confirm | No | ||
| workspace | No | ||
| operation_id | No | ||
| overlap_seconds | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||