bolta.team.rotate_key

Rotate or revoke API keys for principals within a workspace.

2|1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/boltaai/bolta-skills --skill bolta-team-rotate-key
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bolta.team.rotate_key
Source: https://github.com/boltaai/bolta-skills/tree/main/skills/control-plane/bolta.team.rotate_key
Command: npx skills add https://github.com/boltaai/bolta-skills --skill bolta-team-rotate-key

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps manage API keys for principals within a workspace, allowing for secure rotation or revocation to maintain access control and security.

Core Features & Use Cases

  • API Key Rotation: Generate a new API key, replacing an existing one, with an optional new label for easier identification.
  • API Key Revocation: Permanently disable an existing API key.
  • Use Case: As a workspace owner, you need to rotate the API key for an agent that has been compromised or is no longer in use, ensuring no unauthorized access.

Quick Start

Rotate the API key with ID 'key-12345' in workspace 'ws-abcde'.

Frequently Asked Questions about bolta.team.rotate_key

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rotate an API key for a workspace agent?

To rotate an API key, provide the existing key ID and workspace identifier, and the system generates a replacement key with a new preview while enforcing capability checks for secure access control.

When should I revoke an API key instead of rotating it?

You should revoke an API key when permanently disabling access for a compromised or decommissioned principal, whereas rotation replaces the key with a new one to maintain active secure connectivity.

Do I need workspace owner permissions to manage API key revocation?

Yes, managing API key revocation requires passing capability checks within the workspace, ensuring only authorized principals can permanently disable existing keys and maintain access control security.

Can I assign a new label when rotating an API key for easier identification?

Yes, API key rotation supports adding an optional new label to the replacement key, allowing you to easily identify the updated credential within your workspace management interface.

What happens to the old API key after a successful rotation?

After a successful API key rotation, the existing key is replaced by a newly generated credential, providing a new key preview to update your secure integrations and prevent unauthorized access.