transit-engine-encryption-key-create

WHAT IT DOES

What transit-engine-encryption-key-create does on Vault MCP Server (mschuchard)

AI agents use transit-engine-encryption-key-create to create or update resources in Vault MCP Server (mschuchard) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vault MCP Server (mschuchard) environment.

WHY IT NEEDS A POLICY

Why transit-engine-encryption-key-create needs a policy

Creating an encryption key is a write operation that modifies Vault's state by introducing a new cryptographic material resource. While not destructive (keys are not deleted), this action has security implications: a malformed key, weak parameters, or creation in wrong context could compromise encryption operations.

From the tool's definition Tool name 'transit-engine-encryption-key-create' indicates creation of a cryptographic key resource within Vault's Transit engine. The '-create' suffix explicitly signals a write operation that generates a new persistent asset.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transit-engine-encryption-key-create Rate-limited

transit-engine-encryption-key-create 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transit-engine-encryption-key-create": {
      "limits": [
        {
          "counter": "transit-engine-encryption-key-create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Vault MCP Server (mschuchard), so you can run agents against it safely.

FAQ

Questions about transit-engine-encryption-key-create

What does the transit-engine-encryption-key-create tool do? +

transit-engine-encryption-key-create. It is categorised as a Write tool in the Vault MCP Server (mschuchard) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on transit-engine-encryption-key-create? +

Register the Vault MCP Server (mschuchard) MCP server in PolicyLayer and add a rule for transit-engine-encryption-key-create: 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 Vault MCP Server (mschuchard). Nothing to install.

What risk level is transit-engine-encryption-key-create? +

transit-engine-encryption-key-create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit transit-engine-encryption-key-create? +

Yes. Add a rate_limit block to the transit-engine-encryption-key-create 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 transit-engine-encryption-key-create completely? +

Set action: deny in the PolicyLayer policy for transit-engine-encryption-key-create. 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 transit-engine-encryption-key-create? +

transit-engine-encryption-key-create is provided by the Vault MCP Server (mschuchard) MCP server (mschuchard/vault-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.