Skip to content

W-23817598 Add F5 Guardrails Policy documentation - #1147

Open
glenn-rodgers-sf wants to merge 6 commits into
latestfrom
W-23817598-f5-guardrail-policy-gr
Open

W-23817598 Add F5 Guardrails Policy documentation#1147
glenn-rodgers-sf wants to merge 6 commits into
latestfrom
W-23817598-f5-guardrail-policy-gr

Conversation

@glenn-rodgers-sf

Copy link
Copy Markdown
Contributor

Summary

Adds documentation for the F5 Guardrails Policy (from microgateway-hybrid-policies PR #657), a new LLM-category policy that evaluates LLM prompts and responses against F5 AI Guardrails (powered by CalypsoAI) via the POST /backend/v1/scans API and enforces the returned verdict at the gateway (allow / flag / redact / reject).

Changes (gateway/1.13)

  • New page policies-included-f5-guardrails.adoc — modeled on the sibling Azure Content Safety / Bedrock Guardrails docs. Covers configuration (basic + advanced), request/response phases, the outcome→action mapping, per-phase scanner selection, redaction, response headers, metrics, error handling (fail-open/fail-closed + no-verdict), and example configurations.
  • Nav — registered the page alphabetically in nav.adoc.
  • Directory — added an LLM-category row in policies-included-directory.adoc.

Related

  • Release note: mulesoft-emu/docs-release-notes branch W-23817598-f5-guardrail-policy-gr (companion PR).

🤖 Generated with Claude Code

Add the F5 Guardrails Policy page, which evaluates LLM prompts and
responses against F5 AI Guardrails (powered by CalypsoAI), blocking,
flagging, or redacting flagged content. Register the page in the ROOT
nav and the policies directory.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@glenn-rodgers-sf
glenn-rodgers-sf requested a review from a team as a code owner August 12, 2026 16:57
glenn-rodgers-sf and others added 5 commits August 12, 2026 13:04
…erview

Add the F5 Guardrails Policy to the LLM Policies table on the agent
policies page and to the Policy Availability by Gateway table on the
gateways overview page.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Correct the policy page and the Policy Availability by Gateway table to
state that the F5 Guardrails Policy isn't supported in Local Mode,
consistent with the Azure Content Safety and Bedrock Guardrails policies.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Remove the Redaction and Error Handling sections from the F5 Guardrails
Policy page and drop their now-dangling cross-references.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant