identity_set_token_vault_cmk · Awslabs Valkey MCP

WHAT IT DOES

What identity_set_token_vault_cmk does on Awslabs Valkey

AI agents use identity_set_token_vault_cmk to create or update resources in Awslabs Valkey — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Valkey environment.

WHY IT NEEDS A POLICY

Why identity_set_token_vault_cmk needs a policy

The tool name contains 'set', a write operation verb, and references 'token_vault' and 'cmk' (Customer Master Key), implying it modifies token vault settings or encryption key associations. This is a reversible configuration write rather than destructive or financial. However, token/key management operations could have high blast radius if misused (could lock users out, weaken encryption).

From the tool's definition Tool name 'identity_set_token_vault_cmk' suggests setting/writing identity or token configuration related to vault and Customer Master Keys (CMK) in an ElastiCache/MemoryDB context. The 'set' verb indicates a write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

identity_set_token_vault_cmk Rate-limited

identity_set_token_vault_cmk 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": {
    "identity_set_token_vault_cmk": {
      "limits": [
        {
          "counter": "identity_set_token_vault_cmk_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 Awslabs Valkey, so you can run agents against it safely.

FAQ

Questions about identity_set_token_vault_cmk

What does the identity_set_token_vault_cmk tool do? +

identity_set_token_vault_cmk. It is categorised as a Write tool in the Awslabs Valkey MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on identity_set_token_vault_cmk? +

Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for identity_set_token_vault_cmk: 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 Awslabs Valkey. Nothing to install.

What risk level is identity_set_token_vault_cmk? +

identity_set_token_vault_cmk is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit identity_set_token_vault_cmk? +

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

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

identity_set_token_vault_cmk is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.