gcnv_kms_config_delete

Deletes a KMS configuration

Server Google Cloud NetApp Volumes MCP Server netapp/gcnv-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What gcnv_kms_config_delete does on Google Cloud NetApp Volumes MCP Server

AI agents call gcnv_kms_config_delete to permanently remove resources in Google Cloud NetApp Volumes MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why gcnv_kms_config_delete needs a policy

The tool irreversibly deletes KMS configuration, which cannot be undone. This is a destructive action that could compromise encryption key management and access to encrypted data. While not as severe as deleting actual data volumes, removing KMS configuration is a high-impact destructive operation that affects security infrastructure.

From the tool's definition Tool name contains 'delete' and description states 'Deletes a KMS configuration'. KMS (Key Management Service) configurations are critical security infrastructure for encryption key management.

Questions about gcnv_kms_config_delete

What does the gcnv_kms_config_delete tool do? +

Deletes a KMS configuration. It is categorised as a Destructive tool in the Google Cloud NetApp Volumes 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 gcnv_kms_config_delete? +

Register the Google Cloud NetApp Volumes MCP Server MCP server in PolicyLayer and add a rule for gcnv_kms_config_delete: 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 Google Cloud NetApp Volumes MCP Server. Nothing to install.

What risk level is gcnv_kms_config_delete? +

gcnv_kms_config_delete 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 gcnv_kms_config_delete? +

Yes. Add a rate_limit block to the gcnv_kms_config_delete 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 gcnv_kms_config_delete completely? +

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

gcnv_kms_config_delete is provided by the Google Cloud NetApp Volumes MCP Server MCP server (netapp/gcnv-mcp-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.