Delete an InfluxDB token by name (Core/Enterprise only).
AI agents call delete_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.
Deleting a token is an irreversible destructive action that removes authentication credentials from InfluxDB. Once deleted, the token cannot be recovered and any applications or users relying on it will lose access. This represents a high-severity destructive operation with significant blast radius if an AI agent deletes critical tokens without authorization.
From the tool's definition Tool name is 'delete_token' and description states 'Delete an InfluxDB token by name'. The verb 'delete' combined with token management indicates irreversible removal of authentication credentials.
Attacks that exploit this kind of access
Delete an InfluxDB token by name (Core/Enterprise only). 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 delete_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.
delete_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 delete_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 delete_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.
delete_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 →