contract-testing_regenerate_api_token
Regenerate (rotate) an API token by ID. Parameters: - tokenId (string) *required*: ID of the token to regenerate
This record as markdown: /tools/smartbear-mcp/contract-testing-regenerate-api-token.md
What contract-testing_regenerate_api_token does on SmartBear MCP
AI agents call contract-testing_regenerate_api_token to permanently remove resources in SmartBear MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
tokenId | string | Yes | ID of the token to regenerate |
Parameters from the server's own tool schema.
Why contract-testing_regenerate_api_token is rated Critical
Regenerating/rotating an API token permanently invalidates the prior token. Any systems or integrations using the old token will immediately lose access. This is an irreversible operation — the original token cannot be restored — making it Destructive. The blast radius is high because misuse could break authenticated integrations across multiple consumers of that token.
From the tool's definition Regenerate (rotate) an API token by ID — the existing token is invalidated and replaced, which is irreversible (the old token value is permanently destroyed).
Attacks that exploit this kind of access
The rule that runs contract-testing_regenerate_api_token safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For contract-testing_regenerate_api_token, this is the rule to start with:
contract-testing_regenerate_api_token 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 SmartBear MCP, apply this rule, and every contract-testing_regenerate_api_token call is checked against it from then on.
Questions about contract-testing_regenerate_api_token
Regenerate (rotate) an API token by ID. Parameters: - tokenId (string) *required*: ID of the token to regenerate. It is categorised as a Destructive tool in the SmartBear MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
contract-testing_regenerate_api_token accepts 1 parameter: tokenId. Required: tokenId. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_regenerate_api_token: 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 SmartBear MCP. Nothing to install.
contract-testing_regenerate_api_token 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 contract-testing_regenerate_api_token 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 contract-testing_regenerate_api_token. 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.
contract-testing_regenerate_api_token is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartBear, and thousands of servers like it.
Across the catalogue