{"version":"2.1.315","anchor":"gateway-bedrock-guardrail-tagging-and-model-field-validation","canonical_anchor":"gateway-bedrock-guardrail-tagging-and-model-field-validation","heading":"The gateway can tag messages for Bedrock guardrails and checks model fields","tier":"notice","area":"Gateways","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/gateway-bedrock-guardrail-tagging-and-model-field-validation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### The gateway can tag messages for Bedrock guardrails and checks model fields\n\nThe gateway can now wrap message content in Bedrock guardrail tags, and refuses requests with too many or too deeply nested model fields\n\n**Unclear.** How the guardrail tagging mode is chosen is not stated.\n\n**What**\n\nThe gateway, a server bundled with Claude Code that can sit between users and the API, has two new pieces of request handling:\n\n- It can wrap message content in tags that Amazon Bedrock's guardrails (Bedrock's content-filtering feature) read, following one of four modes\n\n- It checks the `model` fields in a request and refuses a request that names more than 100 models or that is nested more than 1,000 levels deep\n\n**Why**\n\nThese change how the gateway handles requests. They do not affect the Claude Code command line itself.\n\n- Area: Gateways\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}