gcp_kms_list_crypto_key_versions
List versions of a crypto key
This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-kms-list-crypto-key-versions.md
What gcp_kms_list_crypto_key_versions does on GCP MCP Server
AI agents call gcp_kms_list_crypto_key_versions to retrieve information from GCP MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gcp_kms_list_crypto_key_versions is rated Low
This is a Read operation; it queries and retrieves information about KMS crypto key versions. However, severity is elevated to 'medium' rather than 'low' because the output could reveal sensitive key version metadata that, if misused by an agent (e.g., to identify outdated or weak key versions for targeting), could inform attacks on the cryptographic infrastructure.
From the tool's definition Tool name and description indicate 'List versions of a crypto key' — a read-only operation that retrieves metadata about cryptographic key versions without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
The rule that runs gcp_kms_list_crypto_key_versions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GCP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gcp_kms_list_crypto_key_versions, this is the rule to start with:
gcp_kms_list_crypto_key_versions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GCP MCP Server, apply this rule, and every gcp_kms_list_crypto_key_versions call is checked against it from then on.
Questions about gcp_kms_list_crypto_key_versions
List versions of a crypto key. It is categorised as a Read tool in the GCP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_kms_list_crypto_key_versions: 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 GCP MCP Server. Nothing to install.
gcp_kms_list_crypto_key_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gcp_kms_list_crypto_key_versions 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 gcp_kms_list_crypto_key_versions. 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.
gcp_kms_list_crypto_key_versions is provided by the GCP MCP Server MCP server (ahmedselimmansor-ctrl/gcp_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GCP MCP Server, and thousands of servers like it.
This server
Across the catalogue