gcp_kms_create_crypto_key
Create a new crypto key in a key ring
This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-kms-create-crypto-key.md
What gcp_kms_create_crypto_key does on GCP MCP Server
AI agents use gcp_kms_create_crypto_key to create or update resources in GCP MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GCP MCP Server environment.
Why gcp_kms_create_crypto_key is rated Medium
This tool creates new cryptographic keys, which is a reversible write operation (keys can be disabled or destroyed later). However, the severity is elevated to 'high' because cryptographic keys are critical infrastructure: misuse could lead to unauthorized key creation, exposure of key management capabilities to unauthorized entities, or proliferation of keys that complicate security auditing.
From the tool's definition Tool name 'gcp_kms_create_crypto_key' and description 'Create a new crypto key in a key ring' directly indicate creation of cryptographic key material in Google Cloud KMS.
Attacks that exploit this kind of access
The rule that runs gcp_kms_create_crypto_key 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_create_crypto_key, this is the rule to start with:
gcp_kms_create_crypto_key stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_create_crypto_key call is checked against it from then on.
Questions about gcp_kms_create_crypto_key
Create a new crypto key in a key ring. It is categorised as a Write tool in the GCP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_kms_create_crypto_key: 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_create_crypto_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gcp_kms_create_crypto_key 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_create_crypto_key. 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_create_crypto_key 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