cloud_delete_database_token

Delete a database token from InfluxDB Cloud-Dedicated cluster. This action cannot be undone.

Server InfluxDB MCP Server quorralyne/mcp_test_server
Category Destructive
Risk class Critical
Parameters 00 required

What cloud_delete_database_token does on InfluxDB MCP Server

AI agents call cloud_delete_database_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.

Why cloud_delete_database_token needs a policy

Token deletion is an irreversible operation that destroys authentication credentials. While not a direct data deletion, removing tokens cannot be undone and impacts access control. This fits the Destructive category (irreversibly deletes). Severity is high because token deletion can break application access and authentication flows, though it does not directly compromise data or move money.

From the tool's definition Tool description explicitly states 'Delete a database token' and 'This action cannot be undone.' The name contains 'delete' and the irreversible nature of token deletion is confirmed.

Questions about cloud_delete_database_token

What does the cloud_delete_database_token tool do? +

Delete a database token from InfluxDB Cloud-Dedicated cluster. This action cannot be undone. 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.

How do I enforce a policy on cloud_delete_database_token? +

Register the InfluxDB MCP Server MCP server in PolicyLayer and add a rule for cloud_delete_database_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.

What risk level is cloud_delete_database_token? +

cloud_delete_database_token is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cloud_delete_database_token? +

Yes. Add a rate_limit block to the cloud_delete_database_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.

How do I block cloud_delete_database_token completely? +

Set action: deny in the PolicyLayer policy for cloud_delete_database_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.

What MCP server provides cloud_delete_database_token? +

cloud_delete_database_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.