Regenerate the InfluxDB operator token (Core/Enterprise only). Returns the new token value. ⚠️ This action invalidates current operator token and is irreversible. Receive the explicit user confirmation before proceeding.
AI agents call regenerate_operator_token to permanently remove resources in InfluxDB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While the tool creates a new token (which could suggest Write category), the irreversible invalidation of the current operator token makes this fundamentally a destructive action. Operator tokens are critical authentication credentials; invalidating them cannot be undone and will break any systems relying on the old token.
From the tool's definition Tool description explicitly states 'This action invalidates current operator token and is irreversible.' Regenerating an operator token irreversibly invalidates the existing token, preventing its future use.
Attacks that exploit this kind of access
Regenerate the InfluxDB operator token (Core/Enterprise only). Returns the new token value. ⚠️ This action invalidates current operator token and is irreversible. Receive the explicit user confirmation before proceeding. It is categorised as a Destructive tool in the InfluxDB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the InfluxDB MCP Server MCP server in PolicyLayer and add a rule for regenerate_operator_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 InfluxDB MCP Server. Nothing to install.
regenerate_operator_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 regenerate_operator_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 regenerate_operator_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.
regenerate_operator_token is provided by the InfluxDB MCP Server MCP server (quorralyne/mcp_test_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →