Set the customer master key (CMK) for an AgentCore Identity token vault. COST WARNING: Switching to a CustomerManagedKey incurs AWS KMS charges for every encryption and decryption request against secrets in the vault (each stored credential). Switching back to ServiceManagedKey stops these KMS c...
Bulk/mass operation — affects multiple targets
Part of the AWS Bedrock AgentCore MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use identity_set_token_vault_cmk to create or modify resources in AWS Bedrock AgentCore MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call identity_set_token_vault_cmk repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS Bedrock AgentCore MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
identity_set_token_vault_cmk:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full AWS Bedrock AgentCore MCP Server policy for all 122 tools.
Agents calling write-class tools like identity_set_token_vault_cmk have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Set the customer master key (CMK) for an AgentCore Identity token vault. COST WARNING: Switching to a CustomerManagedKey incurs AWS KMS charges for every encryption and decryption request against secrets in the vault (each stored credential). Switching back to ServiceManagedKey stops these KMS charges. SECURITY NOTE: This operation changes how credentials stored in the vault are encrypted. Ensure the KMS key policy grants the AgentCore service principal the necessary permissions (kms:Decrypt, kms:Encrypt, kms:GenerateDataKey, kms:DescribeKey) before switching to a CustomerManagedKey, or stored credentials will become inaccessible.. It is categorised as a Write tool in the AWS Bedrock AgentCore MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for identity_set_token_vault_cmk. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Bedrock AgentCore MCP Server MCP server.
identity_set_token_vault_cmk 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 identity_set_token_vault_cmk rule in your Intercept 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 Intercept 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.
identity_set_token_vault_cmk is provided by the AWS Bedrock AgentCore MCP Server MCP server (awslabs.amazon-bedrock-agentcore-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.